<br><br><div class="gmail_quote">2010/9/21 Frank Warmerdam <span dir="ltr"><<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br></div>
The intention of the RFC is that all filenames will be treated as utf-8.<br>
You mention a Changeset.Ansi converter. I assume it is also possible to<br>
do a unicode to utf-8 conversion at the swig interface? It sounds like<br>
all strings that are supposed to be utf-8 as opposed to "locale dependent<br>
C strings" should be identified and a different typemap used for them.<br>
Does that make sense? I have made some note of this in the RFC but I'm<br>
not in a great position to fool with the C# bindings so I'm hoping you<br>
will help with them.<br>
<br></blockquote><div><br>Frank,<br><br>.Net strings are stored as UTF-16 not UTF-8 so passing UTF8 strings in the API will require manual marshaling. Currently the default marshaling behaviour automatically does the UTF-16 to ANSI conversion in the C# interface.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'll note that all the OGR string and stringlist field reading and writing<br>
should also be handled as if the strings are utf-8 per RFC 23. Is that<br>
done currently?<br></blockquote><div><br>No. I'd require the complete list of the functions (and their parameters) for which such kind of manual marshaling should take place. You did mention about stringlists which should always be treated as UTF8, it might be true for OGRFeature.GetFieldAsStringList but not for OGRLayer.CreateLayer for instance.<br>
</div><br></div>Best regards,<br><br>Tamas<br><br>