Changes between Version 8 and Version 9 of MapGuideRfc18
- Timestamp:
- 03/07/07 11:02:24 (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc18
v8 v9 30 30 == Proposed Solution == 31 31 32 Add a new server configuration property "Locale" that can be set to whatever locale the end -users wants.32 Add a new server configuration property "Locale" that can be set to whatever locale the end users wants. 33 33 If this new property is blank or does not exist in the serverconfig.ini file then the server will default to the system locale. 34 34 … … 51 51 The 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 52 53 Backwards 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 .53 Backwards 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 and will need to update their configuration. 54 54 55 55 == Test Plan ==