Darren Dale wrote:
[...]
> What about rendering unicode, but keeping the mpl sources ascii only?
This sounds like the thing to do for now.
While you are at it, perhaps you can figure out how to stop unicode_demo
from generating an error:
driving unicode_demo.py
File "_tmp_unicode_demo.py", line 10
SyntaxError: Non-ASCII character '\xe9' in file _tmp_unicode_demo.py on
line 10, but no encoding declared; see
http://www.python.org/peps/pep-0263.html for details
>
>> Undoubtedly unicode
>> makes sense for the world in the long run, but for me it is an
>> unadulterated pain.
>
> In that case, I imagine you are not eagerly anticipating the arrival of Py3K.
I am fairly open to attempts to make major improvements, or just clean
things up. The unicode aspect of Py3K may make good sense in the long
run, but I expect it will cause me some pain, and I am concerned that
the use of unicode in source code will fragment the world's body of
source code and may be conterproductive. The dominance of English is
not entirely a bad thing, and its loss as a lingua franca may do more
harm than good.
Eric
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
