<br><div class="gmail_quote">2010/9/27 Frank Warmerdam <span dir="ltr"><<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Even, Tamas, Ari, Howard, and other SWIG wise men,<br>
<br>
I got lost last night in the SWIG typemaps we use for GDAL, but eventually<br>
I came up with a minimal patch that seems to make sense and work. I would<br>
appreciate it if you guys could skim it and let me know if I'm doing things<br>
in a really wrong or dangerous way.<br>
<br>
<a href="http://trac.osgeo.org/gdal/attachment/ticket/3766/utf8_swig.patch" target="_blank">http://trac.osgeo.org/gdal/attachment/ticket/3766/utf8_swig.patch</a><br>
<br>
I am attempting to treat any const char * parameter named utf8_path via<br>
a custom typemap that uses the preexisting GDALPythonObjectToCStr() to<br>
convert it. This appears to take regular strings, and unicode strings<br>
properly in Python.<br>
<br></blockquote><div><br>Frank,<br><br>I don't really undestand what's wrong with this. Applying custom typemaps to specific parameters is widely used in the bindings. Those languages will get a warning if that typemap is not yet implemented which is a correct way to notify there should something to be done for that language.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
If I got ahead with this, should I add utf8_path in the README.typemaps?<br>
<br></blockquote><div><br>Yes, it should be documented here what to be implemented in the typemap code. I would also be in favour of adding such typemaps for all other methods requiring utf8 strings in the current interface.<br>
<br>Best regards,<br><br>Tamas<br></div></div><br>