| RAP Internationalization [message #140781] |
Tue, 21 July 2009 02:58  |
Eclipse User |
|
|
|
Hi all,
From RAP tutorial on Internationalization there're at least 2
properties file type created, 1 to handle translation found in
plugin.xml/MANIFEST.MF (plugin.properties) and the other for translation
within our code. For easier maintenance, isn't it advisable to
centralize all the translation into 1 file only (e.g plugin.properties)
? How to call it from within our code without too much performance penalty ?
Any advice would be greatly appreciated.
Regards,
Setya
|
|
|
| Re: RAP Internationalization [message #140922 is a reply to message #140781] |
Tue, 21 July 2009 11:46  |
| Eclipse User |
|
|
|
Hi Setya,
these are two different stories. The message bundle has to reside in the
source tree to be resolved, while the plugin.properties file usually
resides in the bundle root. You may be able to change the latter by
modifying your Bundle-Localization header but I doubt very much that
this simplifies things. I'd recommend to stick to the conventions.
Regards, Ralf
Setya wrote:
> Hi all,
>
> From RAP tutorial on Internationalization there're at least 2 properties
> file type created, 1 to handle translation found in
> plugin.xml/MANIFEST.MF (plugin.properties) and the other for translation
> within our code. For easier maintenance, isn't it advisable to
> centralize all the translation into 1 file only (e.g plugin.properties)
> ? How to call it from within our code without too much performance
> penalty ?
>
> Any advice would be greatly appreciated.
>
>
> Regards,
>
> Setya
|
|
|
Powered by
FUDForum. Page generated in 0.02434 seconds
Home