[mapguide-internals] MapGuide RFC 18 - Localization

Bruce Dechant bruce.dechant at autodesk.com
Thu Mar 8 12:35:46 EST 2007


This affects the SDF and SHP provider. The CPG file is used to define
the locale of the data. This setting is used to define the locale of the
client. The CPG file is used to convert the data to Unicode. This
setting is used to process the Unicode string in context of the client
locale. 

The RDBMS provider are not affected with this setting as all that
processing like toupper is handled in the server and the user have
control over the server setting.

Thanks to Badreddine for clarify with the above statements.

Bruce

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: March 7, 2007 1:50 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization

By the way I just checked the source code for the SHP provider and looks
like cpg files are already supported. See ShapeCPG.cpp under
Providers\SHP\Src\ShpRead. So the SHP provider specifically is not a
good example of why we need this.


Traian


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Wednesday, March 07, 2007 3:45 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization

I thought that one can supply a .cpg file to their SHP fileset that
specifies the code page of the SHP file. This is a standard way to solve
the problem (used by ESRI in ArcPad).


Traian




-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Robert
Bray
Sent: Wednesday, March 07, 2007 3:40 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] MapGuide RFC 18 - Localization

Traian,

It mainly affects one provider SHP, which does not store data in 
Unicode. However I suspect it may also correct sorting issues with SDF.

Bob

Traian Stanev wrote:
> I guess I'm trying to find out if we are trying to fix a problem in a
> specific provider by changing the whole MapGuide process to use the
> locale of one single FDO data source. What if I am connected to two
FDO
> data sources that use different locales? I would like to know what
> "issues" really means.
> 
> Traian
> 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
> Dechant
> Sent: Wednesday, March 07, 2007 2:36 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> Traian,
> 
> There are issues with the MG server being in one locale and the RDBMS
> being in another. By adding this property you could have the MapGuide
> server locale match that of your data (this is the issue that came
from
> FDO).
> 
> Thanks,
> Bruce 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of
Traian
> Stanev
> Sent: March 7, 2007 12:32 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> 
> Doesn't that depend on who executes the code? If the provider is an
> RDBMS running in another process, that could be using a different
locale
> setting from MapGuide itself.  Another thing -- if FDO uses Unicode
> everywhere like its API implies (MapGuide also), is there some sort of
a
> Unicode locale that covers all kinds of string lower/upper/sorting?
> 
> Traian
> 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
> Dechant
> Sent: Wednesday, March 07, 2007 2:27 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> Any provider that does sorting on attribute data or uses SQL
UPPER/LOWER
> functions. Without this change the above does not work as expected.
> 
> Thanks,
> Bruce
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of
Traian
> Stanev
> Sent: March 7, 2007 12:14 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> Which providers in particular require this and in what way?
> 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
> Dechant
> Sent: Wednesday, March 07, 2007 2:04 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> It directly affects them and is part of the reason this RFC is being
> done. :)
> 
> Bruce
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of
Traian
> Stanev
> Sent: March 7, 2007 12:03 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> How will that setting affect FDO providers loaded by the MapGuide
> process?
> 
> Traian
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
> Dechant
> Sent: Wednesday, March 07, 2007 2:01 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> Steve,
> 
> Date/time/currency formatting will use the locale specified. Numbers
> will continue to use the "C" locale internally as they have been.
> 
> Thanks,
> Bruce
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Steve
> Dang
> Sent: March 7, 2007 11:58 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> Hi Bruce,
> 
> I assume this RFC includes some mechanism to switch from user locale
to
> C locale and vice versa, so that date/time/number/currency formatting
> (e.g. MgUtil::StringToDouble, etc.) continues to work.
> 
> Thanks,
> Steve.
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
> Dechant
> Sent: Wednesday, March 07, 2007 11:38 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> Thanks Trevor.
> 
> I'll update the RFC to reflect that the locale is platform specific
and
> does differ between Windows and Linux.
> 
> Bruce
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of
Trevor
> Wekel
> Sent: March 7, 2007 11:31 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> Hi Bruce,
> 
> We also have to be careful with locale on Linux.  We may need to
modify
> the MG_WCHAR_TO_CHAR macro to switch from wchar_t* to localized text.
> On Linux, we currently assume the codepage is unicode compliant and
> convert to UTF-8 text.  So we may need to use iconv to do the codepage
> conversion on Linux.  Also the locale string convention is a little
> different on Linux.
> 
> http://linux.about.com/library/cmd/blcmdl3_setlocale.htm
> 
> Here's a few examples of Linux locale strings:
> 
> en_US
> en_US.iso88591
> en_US.iso885915
> en_US.utf8
> en_ZA
> en_ZA.iso88591
> 
> Thanks,
> Trevor
> 
> 
> 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
> Dechant
> Sent: Wednesday, March 07, 2007 11:08 AM
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] MapGuide RFC 18 - Localization
> 
> The draft RFC 18 specification is now ready for review:
> 
>  
> 
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc18
> 
>  
> 
> Please post any comments to this mailing list.
> 
>  
> 
> Thanks,
> 
> Bruce Dechant
> 
>  
> 
>  
> 
>  
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals



More information about the mapguide-internals mailing list