Eclipse Community Forums: Eclipse Platform » [RCP] Internationalizing Plugins

Home » Eclipse Projects » Eclipse Platform » [RCP] Internationalizing Plugins - about.ini etc

[RCP] Internationalizing Plugins - about.ini etc [message #268311]

Mon, 23 August 2004 16:59

Eclipse User

Can about.ini be internationalized? I've created translated files such as..

about_es_ES.properties
about_en_US.properties

...but strings do not seem to be recognized unless they are in
a regular about.properties.

Preston

Re: [RCP] Internationalizing Plugins - about.ini etc [message #268320 is a reply to message #268311]

Mon, 23 August 2004 18:02

Eclipse User

Originally posted by: richkulp.NO.SPAM.us.ibm.com

For specific settings in the about.ini it will look in the
about.properties for entries that start with %, for example:

# Property "aboutText" contains blurb for "About" dialog (translated)
aboutText=%featureText

It will look for "featureText" in the about.properties file and use that.

--
Thanks, Rich Kulp

Re: [RCP] Internationalizing Plugins - about.ini etc [message #268326 is a reply to message #268320]

Mon, 23 August 2004 18:43

Eclipse User

Rich,

Yes, but what if I have locale-specific blurbs? My translated externalized
strings don't show up even though I've followed the
<base>_<lang>_<country>.properties standard. For example, if I create an
about_es_ES.properties for Spanish-speaking people in Spain, I would think
a %blurb would be read from it if my LANG variable is es_ES. My issue is
that I can't get a locale-specific about.properties file to work;
externalization works fine if I have a single about.properties.

Preston

On Mon, 23 Aug 2004 18:02:56 -0400, Rich Kulp wrote:

> For specific settings in the about.ini it will look in the
> about.properties for entries that start with %, for example:
>
> # Property "aboutText" contains blurb for "About" dialog (translated)
> aboutText=%featureText
>
> It will look for "featureText" in the about.properties file and use that.

Re: [RCP] Internationalizing Plugins - about.ini etc [message #268430 is a reply to message #268326]

Tue, 24 August 2004 12:02

Eclipse User

Originally posted by: richkulp.NO.SPAM.us.ibm.com

I don't know. It works for us. The only blurb we have in the about.ini
is aboutText, so we have:

about.ini:

about.text=%featureText

and in about.properties

featureText=The text to show for feature text.

I don't know what your LANG variable is, but it will load it from
whatever the current locale for your machine is or from the -nl override
option on eclipse.exe

--
Thanks, Rich Kulp

Re: [RCP] Internationalizing Plugins - about.ini etc [message #268504 is a reply to message #268326]

Tue, 24 August 2004 22:41

Eclipse User

Originally posted by: manahan.NOSPAM.ca.ibm.com

You can try putting in a locale directory

plugins/yourplugin_1.0.0/nl/de/DE/about.properties

That seems to work for me.

Peter

Preston Lee wrote:
> Rich,
>
> Yes, but what if I have locale-specific blurbs? My translated externalized
> strings don't show up even though I've followed the
> <base>_<lang>_<country>.properties standard. For example, if I create an
> about_es_ES.properties for Spanish-speaking people in Spain, I would think
> a %blurb would be read from it if my LANG variable is es_ES. My issue is
> that I can't get a locale-specific about.properties file to work;
> externalization works fine if I have a single about.properties.
>
> Preston
>
>
> On Mon, 23 Aug 2004 18:02:56 -0400, Rich Kulp wrote:
>
>
>>For specific settings in the about.ini it will look in the
>>about.properties for entries that start with %, for example:
>>
>># Property "aboutText" contains blurb for "About" dialog (translated)
>>aboutText=%featureText
>>
>>It will look for "featureText" in the about.properties file and use that.
>
>

Re: [RCP] Internationalizing Plugins - about.ini etc [message #268891 is a reply to message #268504]

Thu, 26 August 2004 13:41

Eclipse User

Originally posted by: nick_edgar._no.spam.please_.ca.ibm.com

Correct. The about.properties file is resolved using:
Platform.find(bundle, new Path(NLS_TAG).append(propertiesFilename));
where NLS_TAG is "$nl$".

For example, in the en_CA locale, this gets expanded to nl/en/CA.

For more details, see the Javadoc for Platform.find(Bundle, IPath, Map).

See also
http://help.eclipse.org/help30/topic/org.eclipse.platform.do c.isv/guide/product_def_nl.htm

Nick

"Peter Manahan" <manahan@NOSPAM.ca.ibm.com> wrote in message
news:cggu3u$jvd$1@eclipse.org...
> You can try putting in a locale directory
>
> plugins/yourplugin_1.0.0/nl/de/DE/about.properties
>
> That seems to work for me.
>
> Peter
>
> Preston Lee wrote:
> > Rich,
> >
> > Yes, but what if I have locale-specific blurbs? My translated
externalized
> > strings don't show up even though I've followed the
> > <base>_<lang>_<country>.properties standard. For example, if I create an
> > about_es_ES.properties for Spanish-speaking people in Spain, I would
think
> > a %blurb would be read from it if my LANG variable is es_ES. My issue is
> > that I can't get a locale-specific about.properties file to work;
> > externalization works fine if I have a single about.properties.
> >
> > Preston
> >
> >
> > On Mon, 23 Aug 2004 18:02:56 -0400, Rich Kulp wrote:
> >
> >
> >>For specific settings in the about.ini it will look in the
> >>about.properties for entries that start with %, for example:
> >>
> >># Property "aboutText" contains blurb for "About" dialog (translated)
> >>aboutText=%featureText
> >>
> >>It will look for "featureText" in the about.properties file and use
that.
> >
> >
>

Previous Topic:	BundleException
Next Topic:	How does Eclipse compile files when JRE is configured withing IDE?

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Oct 29 15:40:10 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter