Eclipse Community Forums: Remote Application Platform (RAP)

Home » Eclipse Projects » Remote Application Platform (RAP) » SingleSourcing Localization

SingleSourcing Localization [message #117465]

Mon, 05 January 2009 10:27

Eclipse User

Hi,

I want to make an application multilingual. I did it the RAP way and the
RCP way. I wanted to ask if it is possible to use only one way to
internationalize my application. Is it possible to implement the
localization in the host plug-in of a single sourced application or do I
have to do some platform specific implementations in the regarding
fragments?

Thanks for your answer,

Gunnar Wurl

Re: SingleSourcing Localization [message #117479 is a reply to message #117465]

Mon, 05 January 2009 11:00

Eclipse User

Gunnar,

this has been discussed here before. Search for "I18N with
single-sourcing" for example.

Rüdiger

Gunnar Wurl wrote:
> Hi,
>
> I want to make an application multilingual. I did it the RAP way and the
> RCP way. I wanted to ask if it is possible to use only one way to
> internationalize my application. Is it possible to implement the
> localization in the host plug-in of a single sourced application or do I
> have to do some platform specific implementations in the regarding
> fragments?
>
> Thanks for your answer,
>
> Gunnar Wurl
>

Re: SingleSourcing Localization [message #117936 is a reply to message #117479]

Thu, 08 January 2009 11:05

Eclipse User

Hi,

I read in the german Java Magazin a report about RAP. One thing that
sounded interesting to me was a statement concerning internationalization.
It said that the RAP way of internationalization also works for RCP. So I
wanted to ask how that was meant.

Thanks in advance,

Gunnar Wurl

Re: SingleSourcing Localization [message #118270 is a reply to message #117936]

Mon, 12 January 2009 06:47

Eclipse User

Hi Gunnar,

nice that you read the article. Here are some thoughts about the i18n
problem and how to solve it in RCP and RAP together.

On the one side you could swap your messages classes into fragments
while still having your .properties files in your host bundle. In your
RAP fragment you'd use the RAP approach by utilizing RWT.NLS.
In your RCP fragment you would use the static approach.
One big disadvantage of this approach is that you need to keep two
versions of the Message classes in sync with each other.

Another way would be to have a common accessor class for all your
messages which then has a different implementation for each fragment but
the message classes and .properties files would stay the same.
When looking at the message class in a RAP environment you see that all
have a get() in common to dispatch the message key to the corresponding
translation. That would be the call that you would need to move into one
of the fragments. Using the accessor approach within RCP is no problem.
RCP decided to go with the "static" approach due to performance reasons
(afaik).

Hope this helped a bit to get an idea how to single source the i18n stuff.

Greets
Benny

Gunnar Wurl wrote:
> Hi,
>
> I read in the german Java Magazin a report about RAP. One thing that
> sounded interesting to me was a statement concerning
> internationalization. It said that the RAP way of internationalization
> also works for RCP. So I wanted to ask how that was meant.
>
> Thanks in advance,
>
> Gunnar Wurl
>

Previous Topic:	Closing Frames and Enter Buttons
Next Topic:	toolbar rendering issue.

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Sep 13 14:39:41 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter