Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361113 - [Documentation] Revise documentation for internationalization
Summary: [Documentation] Revise documentation for internationalization
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: Tools (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.1 RC3   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://help.eclipse.org/indigo/index....
Whiteboard:
Keywords:
Depends on:
Blocks: 352265
  Show dependency tree
 
Reported: 2011-10-17 05:30 EDT by Rüdiger Herrmann CLA
Modified: 2013-06-04 05:47 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-10-17 05:30:45 EDT 
The section "How does RAP select the language for a user session?" in the "Internationalization" topic [1] is misleading.
It should point out that the primary language from the Accept-Language header is used as the session-locale and and this is done regardless of the available translations.
To clarify further, we probably should explain how the locale is determined (i.e.how RWT#get/setLocale works ) and then explain how translations are looked up (there is a pointer in the FAQ already [2]) 

[1] http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.rap.help%2Fhelp%2Fhtml%2Fadvanced%2Finternationalization.html
[2] http://wiki.eclipse.org/RAP/FAQ#Why_does_the_Locale_fallback_not_work_as_expected.3F
Comment 1 Ralf Sternberg CLA 2013-06-04 05:47:45 EDT 
I've revised the help on internationalization and tried to focus on the adjustments needed for RAP and multi-user systems in general rather than providing a recipe to follow.
Hope the get/setLocale part is also clearer now. Comments are welcome.