| RCP: i18n for org.eclipse.ui.workbench [message #230265] |
Fri, 16 April 2004 18:47  |
Eclipse User |
|
|
|
Hi,
I'm trying to create a german RCP application. Because there is
currently no language pack available for Eclipse 3.0 I tried to
create one on my own.
Following the "How to Internationalize your Eclipse Plug-In" article
from the eclipse website I created a fragment for org.eclipse.workbench.ui,
copied the package structure of org.eclipse.workbench.ui, then copied all
*.properties files from the eclipse source tree, modified their name by
appending a "_de" to their base name and localized quite a few string,
esp. in the file "org/eclipse/ui/internal/messages_de.properties".
Finally I created a deployment zip of the fragment and copied it
both into the normal eclipse installation plugin folder and into the
plugin folder of the my RCP application installation. I expected the
normal eclipse installation as well as my RCP application to use
my NL fragment when called with the "-nl de_DE" parameter, but instead
nothing at all happened, all string are still shown with the original
english texts.
Any ideas what went wrong, where I made a mistake or how I can debug
the i18n settings used ?
Thanks,
Axel
|
|
|
| Re: RCP: i18n for org.eclipse.ui.workbench [message #230611 is a reply to message #230265] |
Sat, 17 April 2004 22:43  |
| Eclipse User |
|
|
|
Originally posted by: kk.dev.null
Axel Schlueter wrote:
> Hi,
>
> I'm trying to create a german RCP application. Because there is
> currently no language pack available for Eclipse 3.0 I tried to
> create one on my own.
>
> Following the "How to Internationalize your Eclipse Plug-In" article
> from the eclipse website I created a fragment for org.eclipse.workbench.ui,
> copied the package structure of org.eclipse.workbench.ui, then copied all
> *.properties files from the eclipse source tree, modified their name by
> appending a "_de" to their base name and localized quite a few string,
> esp. in the file "org/eclipse/ui/internal/messages_de.properties".
>
Did you convert your "native" properties files to unicode-ascii format
first (using native2ascii)?
You can grab the Eclipse 2.x language packs, do a reverse native2ascii
on the properties files, and then port the needed props files to
3.0. Just add/remove what's in (or not in) 3.0. That is much faster
than trying to translate everything from scratch.
> Finally I created a deployment zip of the fragment and copied it
> both into the normal eclipse installation plugin folder and into the
> plugin folder of the my RCP application installation. I expected the
> normal eclipse installation as well as my RCP application to use
> my NL fragment when called with the "-nl de_DE" parameter, but instead
> nothing at all happened, all string are still shown with the original
> english texts.
>
> Any ideas what went wrong, where I made a mistake or how I can debug
> the i18n settings used ?
>
Not sure about using the "-nl" option. Never tried it. But setting the
system language and locale to the right one, and start up Eclipse, it
works just fine.
If you are on Linux, that's even easier. Just open a terminal, export
LANG to the one you want (if you need special input method, just export
XMODIFIERS too), then start up eclipse from that terminal, and you
can easily test your settings.
|
|
|
Powered by
FUDForum. Page generated in 0.03367 seconds
Home