|
|
Re: Globalization process in RCP app [message #474161 is a reply to message #474158] |
Mon, 21 July 2008 14:58 |
Eclipse User |
|
|
|
Originally posted by: eclipse.maxant.co.uk
what would also be interesting to know is how to internationalise the help.
so far as i know, you need to distribute the correct version with the
language that the installer wants to use. is it possible to translate the
help into several languages, include them all in your plugin, and at
runtime, it chooses the right language based on the -NL parameter passed to
the eclipse instance running your RCP app?
ant
"Velganesh" <svelganesh@gmail.com> schrieb im Newsbeitrag
news:fd3ceadf3d3fe9173b7171eb28cd5af8$1@www.eclipse.org...
> David, AFAIK the process you have mentioned suits externalization of
> string values present in plugin.xml and product manifest. If you are
> looking for ways to convert the label, form title, button name, etc you
> see on the screen into other languages, you should use OSGi's NLS class. I
> couldn't find a suitable example for multiple languages. You can try
> downloading a RCP in other language and check how it has been
> implemented.
>
> You can try this approach.
>
> We call NLS.initializeMessages() in all our classes that extend NLS. You
> pass bundle name and clazz instance. You could compare the current locale
> and load the bundle accordingly. I am not sure if there is an equivalent
> of loading a ResourceBundle for a given locale in Eclipse platform.
>
> http://wiki.eclipse.org/Babel_/_Runtime_Translation_Editor talks about
> your requirement. Also - http://www.eclipse.org/babel/.
>
> Good luck.
>
|
|
|
|
Re: Globalization process in RCP app [message #619279 is a reply to message #474158] |
Mon, 21 July 2008 14:58 |
Eclipse User |
|
|
|
Originally posted by: eclipse.maxant.co.uk
what would also be interesting to know is how to internationalise the help.
so far as i know, you need to distribute the correct version with the
language that the installer wants to use. is it possible to translate the
help into several languages, include them all in your plugin, and at
runtime, it chooses the right language based on the -NL parameter passed to
the eclipse instance running your RCP app?
ant
"Velganesh" <svelganesh@gmail.com> schrieb im Newsbeitrag
news:fd3ceadf3d3fe9173b7171eb28cd5af8$1@www.eclipse.org...
> David, AFAIK the process you have mentioned suits externalization of
> string values present in plugin.xml and product manifest. If you are
> looking for ways to convert the label, form title, button name, etc you
> see on the screen into other languages, you should use OSGi's NLS class. I
> couldn't find a suitable example for multiple languages. You can try
> downloading a RCP in other language and check how it has been
> implemented.
>
> You can try this approach.
>
> We call NLS.initializeMessages() in all our classes that extend NLS. You
> pass bundle name and clazz instance. You could compare the current locale
> and load the bundle accordingly. I am not sure if there is an equivalent
> of loading a ResourceBundle for a given locale in Eclipse platform.
>
> http://wiki.eclipse.org/Babel_/_Runtime_Translation_Editor talks about
> your requirement. Also - http://www.eclipse.org/babel/
>
> Good luck.
>
|
|
|
Powered by
FUDForum. Page generated in 0.04720 seconds