|
Re: Internationalization of "Core Plugins" [message #119882 is a reply to message #119793] |
Tue, 27 January 2009 20:54 |
Eclipse User |
|
|
|
Originally posted by: adv.zahn.googlemail.com
The problem is that - in RAP - the decision for the user's language can
be made for incoming requests. So I think you have to decide
- system output, e.g. when starting the application (locale is the
JVM's system locale)
- UI output, for that you can use the RWT.NLS class
The result is, that - for system output - you cannot use RWT.NLS if you
want to split in core and ui. Instead, you can use ResourceBundles or
the "good old" org.eclipse.osgi.util.NLS class?
Regards,
Ralf
Markus Krüger schrieb:
> Hi,
>
> I have a question. We are developing a new Product with RAP. Usually when
> developing eclipse RCP we split our plugins in "core" and "ui" plugins. The
> "core" plugins usually have no references to any "ui" plugins. Now using
> this concept for RAP seems to fail with internationalization as the class
> "RWT" that is responsible for translation resides in a "ui" plugin.
> Does anyone face the same problem and/or has a solution for this?
>
> Regards,
> Markus
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02946 seconds