Michael Droettboom wrote: > I think the real reason this wasn't done is that its tricky to do at the > C level in a cross-platform way. At present it uses the regular POSIX > fopen in C, which isn't really "Unicode aware".
The actual error is from trying to put the filename in a std::string, but yes, I'm sure the fopen issue is the driver. Does C++ offer anything better? See the "Unicode > filenames" section of the link below for some of the complications. > Linux is particularly hard to get right: > > http://www.amk.ca/python/howto/unicode Thanks, that's a good one. > you can do the following as a workaround > (with a performance hit from making many Python function calls): > > savefig(open(u"CrazyUnicodeFilename.png", "w")) thanks, I'll give that a try. I'm confused, though, why the many Python function calls? the C++ code doesn't just grab the file pointer? Thanks, -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
