Repository model with support for multiple languages
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.
Thanks,
Phong.
Thanks,
Phong.
2 answers
There isn't a recommended technique of shaping a model that needs to
store data in multiple languages. I imagine that the particular problem
you are facing would shape your requirements, and it sounds like storing
multiple content objects for the various translations might work well
for you.
-
Matt Lavin
Jazz Server Team
On Mon, 2009-02-09 at 21:37 +0000, pnle wrote:
store data in multiple languages. I imagine that the particular problem
you are facing would shape your requirements, and it sounds like storing
multiple content objects for the various translations might work well
for you.
-
Matt Lavin
Jazz Server Team
On Mon, 2009-02-09 at 21:37 +0000, pnle wrote:
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.
Thanks,
Phong.