On Monday 16 July 2007 01:25:18 pm Eric Firing wrote: > Michael Droettboom wrote: > > Darren Dale wrote: > >> If not, should we use > >> u'\xd7' or '×' in the actual sources (the latter requiring the file's > >> encoding to be declared at the beginning of the file, like: # -*- > >> coding: utf-8 -*-)? > > > > In an ideal world, I would prefer the latter, but we would want to > > verify that all the matplotlib developers are using an editor that > > respects those tags, or we could run into surprises if the files are > > accidentally re-encoded. > > > > Cheers, > > Mike > > I use a good old-fashioned editor called zed, written by an Italian > named Sandro Serrafini who seems to have left no trace for several > years. I have modified it slightly, and I do minimal maintenance to > keep it compiling with new OS releases. Yes, I am familiar with emacs > and vi and nano and gedit and jed; I periodically survey the field of > editors. And yes, emacs will brew your morning coffee, but no, it won't > behave in the sane ways that I like an editor to behave. > > So the suggestion to start using unicode in source code is a nightmare > for me. Ascii is good: simple, universal, easy to work with, easy to > understand. One byte, one character. Unambiguous.
What about rendering unicode, but keeping the mpl sources ascii only? > 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. ------------------------------------------------------------------------- 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
