| Summary: | RWT.NLS resolves to wrong locale | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Ebert <ralf> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ralf Ebert
Created attachment 160082 [details]
example project
This depends on the '-nl' flag, if the application locale matches the default locale of the 'messages.properties', I get correct behaviour. Is this intentional? This behavior is explained in the JavaDoc of the NLS class.
BUNDLE_NAME contains the name of a properties file (without file extension)
that follows the conventions of standard {@link ResourceBundle} property
files. For each field (in the example 'MyMessage') there has to be a
Please reopen if you disagree.
|