Internationalization of dynamic content content

amy

Hello,

Roo provides an internationalization mechanism for static content but is there anything for dynamic content? For example, the text description of my articles.

If no, what would be the best way to do it, while sticking with Roo?

Thanks

Roo does unfortunately not offer professional translation services. I am sure it would be a great feature though .

Seriously, Roo maintains an application.properties for your your application specific labels. All you have to do is translate it into your language of choice and save it in the same directory as application_lt;codegt;.properties.

HTH,
Stefan

Roo does unfortunately not offer professional translation services. I am sure it would be a great feature though .

Oh yes great idea! Should I open a JIRA?

Seriously, Roo maintains an application.properties for your your application specific labels. All you have to do is translate it into your language of choice and save it in the same directory as application_lt;codegt;.properties.

I understood it and this what I called quot;Static content internalizationquot; in my question.

But in an internationalized CRUD application the managed entities have most likely fields that have to be internationalized (e.g the text description of an Item). Is there something, a mechanism or best practice, to do it with Roo?

Franck

Hi Franck,

I am unclear what you mean by 'something, a mechanism or best practice'. Can you give an example?

As I explained, you need to translate your application.properties files into the languages you need and all should be fine. Not sure how much easier or more 'best practice' advise I can give here

- Stefan

Hi stefan,

you need to translate your application.properties files into the languages you need and all should be fine.

We don't understand each other here. What when a user add a new entity via the GUI? Shall I modify the property file? So why even use a database? No, properties files are unsuitable for what I'm talking about.

As I said, I would like to internationalize some entities fields, those fields that are usually stored in a database, not static fields stored in property file.

A best practice or example could help me to be able add a new language easily without having to change the model.

Franck