Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 373224

Summary:	RWT NLS mechansim broken?
Product:	[RT] RAP	Reporter:	Holger Staudacher <holger.staudacher>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3
Version:	1.5
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Holger Staudacher

2012-03-05 05:25:10 EST

When using RWT NLS the standard Java NLS mechanism is used. As far as I remember this mechanism uses fallbacks for non existing languages. E.g. I have translated strings in messages.properties and messages_de.properties. When I access the UI with en the string in messages.properties will be used because it's the fallback. 

This does not work with RWT. In the scenario above I have to create a messages_en.properties file to be able to access the ui with en. 

Please prove me wrong but I think this is not the standard way?

Comment 1 Ralf Sternberg

2012-03-05 05:51:01 EST

Let me guess: the default locale of your VM is German. In this case, it falls back to German, not English.

Comment 2 Holger Staudacher

2012-03-06 03:04:07 EST

System.out.println(Locale.getDefault()); results in en_US

Comment 3 Holger Staudacher

2012-03-06 03:05:45 EST

I observed this behaviour during two RAP courses. So, if this work for you maybe they had the default locale seted to german.

Comment 4 Ivan Furnadjiev

2012-03-06 05:05:15 EST

Just tested with the RMS demo and the NLS is working for me. Specifying a missing locale fallback to default (which is English in my case).

Comment 5 Ivan Furnadjiev

2012-03-06 05:12:11 EST

Holger, I will close it as invalid. Please reopen it if you reproduce it again.