> 4. Make sure your editor is correctly saving the file in that
> specified encoding. This is perhaps the hardest step because editors
> all handle it a little differently. Some editors have an option
> somewhere to set the encoding that files are saved in. Others may
> automatically understand the "coding" comment line in the file. (Same
> goes for any terminal emulator you may be using for interactive plotting.)
>
> If you can't get step 4 to work successfully, you can write Unicode
> strings in Python using only ASCII characters using the "\u0000" escape
> sequence.
>
> u"Flamb\u00e9e"
>
> (Here, the Unicode code point for e with accent-aigu is 00E9).
I think this may be the obvious problem (I don't how to change the encoding
in pycrust :|)
So, following all of the above, the attached works fine for me with .eps
> output on 0.91.2. (There were various Unicode issues in 0.90.x that
> were fixed.) If it still doesn't work for you, please let us know.
>
I'll try this (I think the 3D stuff still works with this version, doesn't
it ?)
Matthieu
--
French PhD student
Website : http://matthieu-brucher.developpez.com/
Blogs : http://matt.eifelle.com and http://blog.developpez.com/?blog=92
LinkedIn : http://www.linkedin.com/in/matthieubrucher
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
