Changes between Version 9 and Version 10 of MapGuideRfc45

Timestamp:

01/28/08 12:05:26 (17 years ago)

Author:

waltweltonlair

Comment:

--

MapGuideRfc45

@@ -42 +42 @@
 !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.
 
+The web tier methods !EnumerateApplicationContainers, !EnumerateApplicationWidgets, and !EnumerateApplicationTemplates look for a subfolder that matches the locale code.  They will also need to be updated to try the "parent" codes of the extended codes if they cannot be found (e.g. if "zh-CN" cannot be found, look for "zh").
+
+The session affinity code requires parsing of a session ID, which contains the locale.  This code will be looked at to determine if the use of extended codes requires any modifications.
+
 
 == Implications ==
-
 There are no backwards compatibility issues: HTTP requests using the basic format will continue to work.
 
@@ -50 +53 @@
 
 Extended format resource files need to use the (lower)-(upper) convention (matters in Linux where filenames are case-sensitive).
+
+The Fusion framework uses the locale passed in by the LOCALE url parameter to determine which string bundles to load – it may require minor modifications to support extended locale codes.  DM Solutions would be required to make the changes, which are most likely trivial.