Managing support for multiple languages in RTC
Hi,
I'm back with the RTC support for multiple languages, and I'm looking for tips on how to manage this to minimize process template maintenance.
Basically, this is my understanding for the process:
0. I have an externalized process template, that supports multiple languages as properties files are provided as attachments within the template.
-- Let's assume I need to make further changes on this process template. As it is not very friendly to work directly with the externalized strings, instead of making the changes directly on the process template, I do the following:
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.
-- Here is my point:
4. The resulting Process Template is not externalized. Even if the locale specific message files are retained, all the variables have gone. So I need to externalize the process template again! This could be much time consuming depending the amount of customizations you have done into the template.
Is this the right way to manage this? Is there any way to minimize the process template maintenance? Any suggested reading? Any plans to improve this?
Thanks a lot for your guidance,
--Claudia
I'm back with the RTC support for multiple languages, and I'm looking for tips on how to manage this to minimize process template maintenance.
Basically, this is my understanding for the process:
0. I have an externalized process template, that supports multiple languages as properties files are provided as attachments within the template.
-- Let's assume I need to make further changes on this process template. As it is not very friendly to work directly with the externalized strings, instead of making the changes directly on the process template, I do the following:
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.
-- Here is my point:
4. The resulting Process Template is not externalized. Even if the locale specific message files are retained, all the variables have gone. So I need to externalize the process template again! This could be much time consuming depending the amount of customizations you have done into the template.
Is this the right way to manage this? Is there any way to minimize the process template maintenance? Any suggested reading? Any plans to improve this?
Thanks a lot for your guidance,
--Claudia