support for localization and pseudo-localization

fmcgrath wrote:

How will the Jazz support for localization be implemented, and will it
support localized server, eclipse client, and web ui?

We're externalizing our strings to properties files which can be
translated to other locales. Here's a couple of wiki articles you might
find interesting:
https://jazz.net/wiki/bin/view/Main/ExternalizingStrings
https://jazz.net/wiki/bin/view/Main/WebUIExternalization

As Jazz adds support for localization, will it also add support for
pseudo-localization. For example, supporting the use of a locale 'zz' to
trigger use of the pseudo-localized strings? How might this work for web
ui?

With all strings externalized, I'd think that pseudo-localization
testing would be pretty straightforward, but I'm not too familiar with
the technique. Are there any hidden pitfalls?

Thanks,
Craig

"Craig Chaney" <craigcw> wrote in message
news:g6vkq5$gkv$1@localhost.localdomain...

fmcgrath wrote:
How will the Jazz support for localization be implemented, and will it
support localized server, eclipse client, and web ui?

We're externalizing our strings to properties files which can be
translated to other locales. Here's a couple of wiki articles you might
find interesting:
https://jazz.net/wiki/bin/view/Main/ExternalizingStrings
https://jazz.net/wiki/bin/view/Main/WebUIExternalization

As Jazz adds support for localization, will it also add support for
pseudo-localization. For example, supporting the use of a locale 'zz' to
trigger use of the pseudo-localized strings? How might this work for web
ui?

With all strings externalized, I'd think that pseudo-localization testing
would be pretty straightforward, but I'm not too familiar with the
technique. Are there any hidden pitfalls?

Thanks,
Craig

Well - properties files work for Java pretty well. But they are not as well
supported in javascript for use in web ui. There is a mechanism defined in
dojo.i18n, but this mechanism does not support putting the translations into
nls fragments within the jazz framework (or at least we can't get it to
work).

Frank

Is there a recommended technique to model the storage of a Jazz component in a way that a single repository can support multiple languages? Our persisted data is separated in 2 parts: model (objects and their relationships) and content (textual properties of the objects), and the content must be translated in in different languages. In other words, we would have many contents, one for each language, that are sharing the same model. Depending on the locale setting of the logged-on user, content is user's locale will be served to the user.