Home › Forums › Development › Localization is not happening in french for Sectors under holdings
- This topic has 5 replies, 4 voices, and was last updated 8 years, 11 months ago by
ashutosh.
-
AuthorPosts
-
-
October 22, 2015 at 10:41 am #338
ashutosh
ParticipantDear Team,
contacts -> Portfolio -> Accounts -> Holdings -> Assets and Detailed Assets. Here English locale is working as expected. When locale has been changed to French the French locale is not reflecting in the respective fields i.e. its coming in English.
Please suggest if we are missing something
Thanks
0 -
October 23, 2015 at 2:05 pm #346
Ed Shaw
KeymasterThanks for your question.
From the sounds of it, the rest of the UI is showing the correct french text, but the holdings and sectors part of the screen aren’t.
What version are you working with? Is it software under development – i.e. Jade? Or is it a released version. If it is Jade then likely the string files haven’t been translated yet or they are values coming from a rows in a database that don’t get translated.
If that is the case, this will be addressed before final QA.
0 -
October 23, 2015 at 4:51 pm #339
Peter Murray
ParticipantRun-time localization is mostly stored in the TypeLocalization table. There is a row for each locale. On the localized class, the caption attribute is a calculated attribute that shows the caption of the currently selected locale. The name property by convention is a non-localized attribute.
Please make sure the correct localized captions are in the database for the objects you are looking at. If so, perhaps the UI is bound to the non-localized name attribute instead of the caption calculated attribute.
1-
October 23, 2015 at 4:58 pm #341
Ed Shaw
KeymasterThat was the case. The list column was bound to the name attribute and not the caption attribute.
As Peter mentioned, for classes with the LOCALIZABLE_CAPTION aspect applied, the name attribute contains the non localized value and the caption attribute contains the localized caption.
0 -
October 23, 2015 at 6:13 pm #343
ashutosh
ParticipantThank you Peter. It worked after changing the value from name to current localization caption.
0
-
-
-
AuthorPosts
- You must be logged in to reply to this topic.