On May 17, 2012, at 2:55 AM, Zdravko Subakov wrote:
> Beside just translating some of the menus to local languages Id like to
> dinamicly change UI for example: labels, menus etc for users prefered
> language. The idea is to store each textual component with a veriosns for
> each language in a database and then retrieve it as needed. Is there
> something I should be aware of ia there the proper way of doing it?
We are using the standard GNU gettext strategy for localization: wrap
localized strings in the _() function, and then use the gettext tools to
extract those strings and translate them dynamically. The translations are
managed at https://translations.launchpad.net/dabo/ - if you have a Launchpad
account and speak a language other than English, you can help the project by
translating as much of the framework as you can into your language.
That said, this only helps for the framework strings; if you have your
own strings for your app that need localization, there (currently) is no way to
handle this. I could see extending the dLocalize class to work with both the
framework translations as well as the app-specific translations, but I would
imagine that this would not be a simple thing to do. Can you add a ticket for
this so that it doesn't get forgotten? The ticketing system for dabo is at
http://trac.dabodev.com
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]