Eclipse Community Forums: Rich Client Platform (RCP)

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » RCP and i18n

Show: Today's Messages :: Show Polls :: Message Navigator

RCP and i18n [message #436334]

Tue, 06 September 2005 10:21

Fabian Wolf

Messages: 96
Registered: July 2009

Member

Hi all,

I'm kinda puzzled, what exactly is required to get internationalization
working in a RCP application, especially SWT's and GEF's translations. The
problem is not getting all the strings externalized - this works as
expected.

SWT documentation says its swt-nl.jar just needs to be on classpath for
translations to work. How would I bundle it together with my exported app?
Any settings in pluxin.xml/MANIFEST.MF?

GEF's translations are shipped as fragment, how would I tell my app about
it? Adding it as dependancy doesn't work. Neither does putting the content
in my apps feature and plugin directory.

All the how-tos about plugin internationalization just seem to cover
externalization of strings, not how to get required plugin's translations
to work.

Thank you all a lot in advance!

Fabian

Report message to a moderator

Re: RCP and i18n [message #436352 is a reply to message #436334]

Wed, 07 September 2005 02:46

Pascal Rapicault

Messages: 440
Registered: July 2009

Senior Member

There is nothing special to do to have your app translated.
At development time, make sure you have all the fragments for all your
plugins loaded into your application. Once deployed make sure those
translation fragments are present as well.

To specify a language you need to start with -nl XXXX on the command
line (or osgi.nl=XXXX in the config.ini in 3.1) where XXXX is the locale
for the language you want to run with.

If you don't see the translation, start with -console on the command
line and see if the fragments are resolved.

PaScaL

Fabian Wolf wrote:
> Hi all,
>
> I'm kinda puzzled, what exactly is required to get internationalization
> working in a RCP application, especially SWT's and GEF's translations. The
> problem is not getting all the strings externalized - this works as
> expected.
>
> SWT documentation says its swt-nl.jar just needs to be on classpath for
> translations to work. How would I bundle it together with my exported app?
> Any settings in pluxin.xml/MANIFEST.MF?
>
> GEF's translations are shipped as fragment, how would I tell my app about
> it? Adding it as dependancy doesn't work. Neither does putting the content
> in my apps feature and plugin directory.
>
> All the how-tos about plugin internationalization just seem to cover
> externalization of strings, not how to get required plugin's translations
> to work.
>
> Thank you all a lot in advance!
>
> Fabian

Report message to a moderator

Previous Topic:	Printing abstraction layer for SWT
Next Topic:	Title of PreferenceDialog

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Dec 08 19:48:11 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter