I wrote:
> a glitch, at least. the _imagingft driver appears to use Python's
> default encoding, rather than the filename encoding.
>
> should be relatively easy to fix, I think
For the record, here's a (preliminary) patch:
$ svn diff _imagingft.c
Index: _imagingft.c
===================================================================
--- _imagingft.c (revision 3349)
+++ _imagingft.c (working copy)
@@ -117,9 +118,17 @@
static char* kwlist[] = {
"filename", "size", "index", "encoding", NULL
};
+
+#if defined(HAVE_UNICODE)
+ if (!PyArg_ParseTupleAndKeywords(args, kw, "eti|is", kwlist,
+ Py_FileSystemDefaultEncoding,
&filename,
+ &size, &index, &encoding))
+ return NULL;
+#else
if (!PyArg_ParseTupleAndKeywords(args, kw, "si|is", kwlist,
&filename, &size, &index, &encoding))
return NULL;
+#endif
if (!library && FT_Init_FreeType(&library)) {
PyErr_SetString(
</F>
_______________________________________________
Image-SIG maillist - Image-SIG@python.org
http://mail.python.org/mailman/listinfo/image-sig
