Changes between Version 2 and Version 3 of MapGuideRfc45

Timestamp:

01/27/08 20:20:17 (17 years ago)

Author:

waltweltonlair

Comment:

--

MapGuideRfc45

@@ -29 +29 @@
 == Motivation ==
 
-TBD
+A two-letter language code is sometimes insufficient to distinguish between the different variations of a language.  Chinese is a good example.  Using just a two-letter language code ("zh" for Chinese) does not allow a localization distinction between the two languages "Simplified Chinese" and "Traditional Chinese".  However with the proposed extended format these would be encoded as "zh-CN" and "zh-TW".
 
 
 == Proposed Solution ==
 
-TBD
+For !MapGuide, the HTTP Accept-Language header is a reasonable way to determine the language:
+
+http://www.w3.org/International/questions/qa-accept-lang-locales.
+
+The value of the header is generally encoded as [language]-[country], such as en-us, en-gb, zh-cn, or zh-tw.  The country can be upper or lower case.  HTTP also accepts just "en" or "zh".
+
+!MapGuide platform code will be extended to accept both formats.  Resource filenames would also follow this convention (e.g. "mapguide_zh-CN.res", or just "mapguide_zh.res").  A browser can make a request using either the extended format ("zh-CN") or the basic format ("zh").  If the extended format is requested and those resources are not found, then we default to the basic format.  In other words, "zh-CN" should default to using "zh" resources if "zh-CN" resources are not present.
 
 
 == Implications ==
 
-TBD
+When providing resource files that use the extended format, a default file that uses the basic format must also be provided.  This can simply be a copy of one of the extended versions.