Changes between Version 4 and Version 5 of MapGuideRfc45

Timestamp:

Jan 27, 2008, 8:40:30 PM (16 years ago)

Author:

waltweltonlair

Comment:

--

MapGuideRfc45

@@ -29 +29 @@
 == Motivation ==
 
-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 uniquely encoded as zh-CN and zh-TW.
+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 using the proposed extended format these would be uniquely encoded as zh-CN and zh-TW.
 
 
@@ -40 +40 @@
 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.  To simplify the permutations we could convert to a (lower)-(upper) convention, i.e. zh-cn would become zh-CN.  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.
+!MapGuide platform code (MgUserInformation::!SetLocale) will be extended to accept both formats.  To simplify the permutations we will convert to a (lower)-(upper) convention, i.e. zh-cn would become zh-CN.  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 or the basic format.  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.
 
 
@@ -52 +52 @@
 == Test Plan ==
 
-TBD
+