Changes between Version 6 and Version 7 of MapGuideRfc18


Ignore:
Timestamp:
03/07/07 10:56:47 (18 years ago)
Author:
brucedechant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc18

    v6 v7  
    2626== Motivation ==
    2727
    28 The reason for adding better localization support is for better support of end-users that are not using English.
     28The reason for adding better localization support is for better support of end-users that are not using English. This will allow sorting and using of Upper/Lower string functions on non-English data.
    2929
    3030== Proposed Solution ==
     
    4444French_France.1252
    4545
     46Please see developer documentation for the setlocale() API for more information on the locale examples.
     47
     48
    4649== Implications ==
    4750
    4851The current server configuration property "!DefaultLocale" will be renamed to reflect what the property really does. The proposed new name is "!DefaultMessageLocale" because the property is only for the locale of messages returned to clients that have not specified their locale themselves. The format for this property will remain the same, ie: ISO639-1 name.
     52
     53Backwards compatibility is partially maintained because if the user is already using "DefaultLocale" with a value of "en" for English messages the new "DefaultMessageLocale" has a value of "en" by default. However, if they have changed to some other value they will be affected.
    4954
    5055== Test Plan ==