Home Forums Development Localization is not happening in french for Sectors under holdings

Viewing 2 reply threads
  • Author
    Posts
    • #338
      ashutoshashutosh
      Participant

      Dear 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
    • #346
      Ed ShawEd Shaw
      Keymaster

      Thanks 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
      • #348
        ashutoshashutosh
        Participant

        Hi Ed,

        We are using Jade. Could you please provide us the table name where localization data is getting saved in the database.

        Thanks.

        0
    • #339
      Peter MurrayPeter Murray
      Participant

      Run-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
      • #341
        Ed ShawEd Shaw
        Keymaster

        That 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
      • #343
        ashutoshashutosh
        Participant

        Thank you Peter. It worked after changing the value from name to current localization caption.

        0
Viewing 2 reply threads
  • You must be logged in to reply to this topic.