Hi Chris,

this is a bit annoying. I have the same issues and this is what I am doing....

First, the language set on the server is captured at project creation time and that somehow sets the default language.

To change the default language for Apache locate the server.startup script.
In the bottom area and look for

set JAVA_OPTS=-Djava.awt.headless=true -DSQLSERVER_JDBC="%SQLSERVER_JDBC%"........

Add -Duser.language=en_US see below

set JAVA_OPTS=-Duser.language=en_US -Djava.awt.headless=true -DSQLSERVER_JDBC="%SQLSERVER_JDBC%"........

To change the language for Eclipse locate the eclipse.ini in the eclipse installation directory and add -Duser.language=en_US to the VM args.

For example my eclipse.ini looks like:

-startup
plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-vm
jdk\jre\bin
-vmargs
-Xms100m
-Xmx512m
-Xjit:exclude={com/ibm/team/coverage/internal/common/report/SourceElementInfo.write*}
-Dosgi.requiredJavaVersion=1.5
-Dosgi.bundlefile.limit=100
-Duser.language=en_US

To avoid some pages showing up in the Firefox borwser I had to set it to english language as preferred and remove all others.

Thanks,

Ralph

Hi Chris,

that is strange. It works for me. I don't know why it shouldn't work for you then.

Does anyone else have an idea?

Ralph

On Fri, 07 Aug 2009 13:23:02 +0000, c_balthaus wrote:

Aaaaaaaaaah! :D

I've got it solved:
There a slightly different way with another parameter for switching the
language which Eclipse

With exactly your notation
-Duser.language=en_US
in the ini-File it's now working

Thank you!

If you want to set the locale to en_US, I think you should actually split
it up using these two properties:

-Duser.language=en
-Duser.region=US

If you're familiar with the java.util.Locale class, there are separate
fields for language and region. The way you're setting the property now,
the Locale object will end up looking like this:

Locale {
language = en_US
region = null
}

This is wrong. It will *often* work because of how the object computes
its toString, but it you could also get unexpected behavior at times. If
you use the two properties, the Locale will actually be correct:

Locale {
language = en
region = US
}

--
Jared Burns
Jazz Process Team

I will put that into my lessons learned, thanks Jared

Ralpj

I would recommend taking a slightly different route, when editing the eclipse.ini file, instead of adding Duser.language at the end, add these two lines after the "--launcher.library" line and the line beneath it.

-nl
en_US

I say this because I was having issues getting the RTC client to load properly in pt_BR versus pt_PT whilst taking the 'Duser.language=' route. Here is the link to the Java 7 Supported Locale Page but I'm pretty sure RTC only runs in

Simplified Chinese     -nl ZH
Traditional Chinese     -nl ZH_TW
Japanese     -nl JP
Korean     -nl KO
French     -nl FR
German     -nl DE
Italian     -nl IT
Spanish     -nl ES
Portuguese(Brazil)     -nl PT_BR
Czech     -nl CS
Russian     -nl RU
Polish     -nl PL
Hungarian     -nl HU