Hi!
There are two RFCs regarding the Unicode issues:
RFC #5: http://trac.osgeo.org/gdal/wiki/rfc5_unicode
RFC #23: http://trac.osgeo.org/gdal/wiki/rfc23_ogr_unicode
RFC #23 seems to be adopted for GDAL 1.6. But to me it is not that clear,
which functions/methods do:
1. always return/accept UTF-8 strings (e.g. OGRFeature::SetField(),
OGRFeature::GetFieldAsString() (or is this also based on the capability
flag), any other functions?, what about GetFieldName()?)
2. can return/accept UTF-8 and also Ansi-encoded strings, based on the
capabilities of the underlying driver
3. always return/accept Ansi-encoded strings (e.g. GDALOpen()?)
The state of RFC #5 is "in development". What does this mean? It has been
partially implemented, or it is currently in the implemented phase in a
separate branch, to merge back the changes into the main development branch
after a successful implementation?
Thanks for clarification,
Kosta
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
