This depends on the installation circumstances. Most
Software is only used in one language for one
installation. Then the data in the database are in
the language and that's it.
The only thing that is localized is the GUI.
Localization driven by database is only posible if
the software is strictly driven by database contents
Every free text is a problem.
Andrus Adamchik <andru..bjectstyle.org> schrieb am 24.08.04 21:26:36:
>
> Hi Kevin,
>
> As you correctly noticed, there is no special support for attribute
> localizing in Cayenne. And your suggestion for the possible solution
> seems very reasonable. So I'd like to add this idea to Cayenne roadmap.
> Until this gets implemented, I guess localization can be done at the
> DataObject level by manually creating locale-aware "delegating"
> getters.
>
> As I personally don't have much experience in working with localized
> database schemas, I wonder how many people actually care about
> localized DB data (just to prioritize this I guess)? I can see how it
> can be useful for "configuration" tables used to build app labels,
> dropdowns, and such. Still most "dynamic" data is probably entered in
> just one language for each record, no matter how many total languages
> application supports.
>
> Andrus
_______________________________________________________
WEB.DE Video-Mail - Sagen Sie mehr mit bewegten Bildern
Informationen unter: http://freemail.web.de/?mc=021199
This archive was generated by hypermail 2.0.0 : Wed Aug 25 2004 - 03:02:49 EDT