Home » Support » Telligent Evolution Platform » Telligent Enterprise » Discussions » Language packs

Language packs

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 9 Replies
  • 0 Subscribers
  • Posted8 months ago
Options

Language packs

This question is answered
RenierW
Posted by
on Tue, Sep 4 2012 6:20 AM

Hi Everyone,

I have created a new language pack by doing the following:

- Copied the en-US files to en-AU

- Added the language to the languages.xml file

-Created a communityserver_override.config file and override the defaultLanguage attribute to en-AU.

As far as I know this is all you should do, but if I reload the site, all the text have MISSING RESOURCE: infront of them, although that resource is in the resources.xml file that was copied.

All the language drop down fields have defaulted to en-AU though.

If I change the override config file back to en-US, all is fine again.

Any suggestions, or did I miss something?
Verified Answer
  • Michael Monteleone
    Posted by
    on Tue, Sep 4 2012 4:47 PM
    Verified Answer
    Verified by

    Hi.  Are you using a version of Evolution greater than 6.0?  If so, it's important to note that widgets now define their own resources.  The resources defined within the *.xml files are only for platform-wide and legacy resources.  

    Resources can be edited and added for languages within Widget Studio by editing a widget and navigating to its 'Resources' tab.  The drop-down will show a list of installed languages and will highlight resources defined by the widget which are not defined for the selected language.

    However, the typical process for translating widget resources is to export the widgets' resources, translate, and re-import.  Some documentation for this exists here:  telligent.com/.../managing-widgets.aspx
  • Michael Monteleone
    Posted by
    on Wed, Sep 5 2012 3:09 PM
    Verified Answer
    Verified by

    Hi Renier,

    Yes, starting with Enterprise 3.0, widget resources are included directly within widgets and are not translated as part of languages.xml.  This enables greater upgrade safety and portability of widgets.  And since widgets are exported with themes, this also enables packaging of pre-localized themes.

    In practice, this should just mean the addition of a single extra translation file (in addition to the aforementioned languages.xml) exported from Widget Studio once for all widgets, then translated, and then re-imported into Widget Studio).  

    Hope this helps

    edit: typo
All Replies
  • Michael Monteleone
    Posted by
    on Tue, Sep 4 2012 4:47 PM
    Verified Answer
    Verified by

    Hi.  Are you using a version of Evolution greater than 6.0?  If so, it's important to note that widgets now define their own resources.  The resources defined within the *.xml files are only for platform-wide and legacy resources.  

    Resources can be edited and added for languages within Widget Studio by editing a widget and navigating to its 'Resources' tab.  The drop-down will show a list of installed languages and will highlight resources defined by the widget which are not defined for the selected language.

    However, the typical process for translating widget resources is to export the widgets' resources, translate, and re-import.  Some documentation for this exists here:  telligent.com/.../managing-widgets.aspx
  • Miles Dunn
    Posted by
    on Tue, Sep 4 2012 4:52 PM

    Hi Renier,

    That sounds right to me.  

    so, IF:

    1. en-AU lang pack is installed

    2. communityserver_override.config being set to use en-US

    Can you go into a user's profile and change it to use en-AU?

    When logging in as that user, does the en-AU lang pack work correctly?

    Regards,

    Miles Dunn

    Telligent
  • RenierW
    Posted by
    on Wed, Sep 5 2012 10:11 AM

    Hi Michael,

    Thank you for your help.

    Yes, I'm using Telligent Enterprise 4.0 Beta.

    Is there no other way of setting all of those widget's language to the new one?

    Regards,

    Renier
  • RenierW
    Posted by
    on Wed, Sep 5 2012 10:12 AM

    Hi Miles,

    Thanks, yes this works in the previous version, I'm using Telligent Enterprise 4.0 Beta.
  • Michael Monteleone
    Posted by
    on Wed, Sep 5 2012 3:09 PM
    Verified Answer
    Verified by

    Hi Renier,

    Yes, starting with Enterprise 3.0, widget resources are included directly within widgets and are not translated as part of languages.xml.  This enables greater upgrade safety and portability of widgets.  And since widgets are exported with themes, this also enables packaging of pre-localized themes.

    In practice, this should just mean the addition of a single extra translation file (in addition to the aforementioned languages.xml) exported from Widget Studio once for all widgets, then translated, and then re-imported into Widget Studio).  

    Hope this helps

    edit: typo
  • RenierW
    Posted by
    on Thu, Sep 6 2012 1:11 AM

    Hi Michael,

    Thanks for the help, appreciated!
  • RenierW
    Posted by
    on Thu, Sep 6 2012 1:11 AM

    Hi Michael,

    Thanks for the help, appreciated!
  • RenierW
    Posted by
    on Tue, Sep 11 2012 12:23 AM

    Hi Michael,

    I was thinking about the following:

    If we only want one language pack anyway i.e. "en-au", can't we just rename the text in the language file and keep the key="en-us".

    Instead of duplicating everything and pointing to the right one.

    Will this be upgrade safe, but I guess it will not right? :)

    Thanks
  • Wyatt Lyon Preul
    Posted by
    on Tue, Sep 11 2012 3:32 PM

    You could do this, especially since there probably aren't a lot of changes anyway.