Internationalization... how to?

BIRT has built-in localization support.
When deploying the BIRT report templates, you will need to also deploy the property files with those.

Rafik,
Is that deployed as the "resources" for the report you are deploying?

Yes.

On Wed, 16 Dec 2009 02:22:55 +0000, ccalleg wrote:

Hi,
I have a RTC proc.template available in English and would like to make
it available in other languages. Based on what I have read, I have to
externalize the strings, so I will have several "message.properties"
files depending on the languages I am providing.

My questions are:
a) this seems to be a tedious manual effort. Do you have any tip on how
to speed up this manual process? Any suggestion for this?

b) how can I provide translation for Birt reports that are NOT out of
the box?

Thanks
Claudia Callegari

Hi, Claudia.

To answer your first question, we don't really have any tips for speeding
up the process.

--
Jared Burns
Jazz Process Team

Usually I work on a project area and then create a new process template out of it.
The thing is that when creating a PA, all the % references are gone. And if I create a template out of that PA, it won't be translatable, because the new template won't have %references to messages.

Is there any way to fix this?

Thanks in advance!

Usually I work on a project area and then create a new process template out of it.
The thing is that when creating a PA, all the % references are gone. And if I create a template out of that PA, it won't be translatable, because the new template won't have %references to messages.

Is there any way to fix this?

Thanks in advance!

Hi,

I assume you would have followed the steps given below

1. Create a PA using an externalized Process Template choosing a particular locale. On doing so the %references in Process Template will be replaced by translated message strings.
2. Make some modifications to the Process in context of the created PA.
3. Create a new Process Template out of the PA.
4. The resulting Process Template is not externalized. But the locale specific message files are retained, so it should help with speeding up the procedure to externalize the process template.

Thanks
Sridevi
Jazz Process Team

On Mon, 11 Jan 2010 14:23:03 +0000, tgau wrote:

Does this mean that RTC does not support team with members speaking
different languages?

Desired scenario:
A NLS-enabled process area (not process template) so RTC displays
french/german/spanish strings based on the language selection of the
user.

The RTC-buttons support this, so should the team process.

Is this supported in 2.0.0.2 or not?
If not, any plans to support this?

Everything about the tool gets translated into the user's locale. The
only thing that doesn't get translated is your own content. That is, the
team's process XML.

--
Jared Burns
Jazz Process Team

Does this mean that RTC does not support team with members speaking different languages?

Desired scenario:
A NLS-enabled process area (not process template) so RTC displays french/german/spanish strings based on the language selection of the user.

The RTC-buttons support this, so should the team process.

Is this supported in 2.0.0.2 or not?
If not, any plans to support this?