Not everyone can easily use a text editor which recognizes all non- ASCII character properly, so I think we should be careful about this.
- kcrisman On Jan 21, 9:09 am, Gonzalo Tornaria <torna...@math.utexas.edu> wrote: > On Thu, Jan 21, 2010 at 3:22 AM, Pat LeSmithe <qed...@gmail.com> wrote: > > Should we put > > > # -*- coding: utf-8 -*- > > > at the top of all .py and .pyx(?) files in the Sage library? > > > I think this will allow us to use Unicode literal strings in Sage code, > > doctests, documentation --- without raising coding errors. > > I had to patch sagenb b/c doctests don't display in the notebook when > they have utf-8 (this was rc0, > > However, I just discovered that the sagenb (in > local/lib/python2.6/site-packages/sagenb-0.5-py2.6.egg/sagenb) is not > under hg, so I will need to dig what I actually changed... > > The relevant ticket ishttp://trac.sagemath.org/sage_trac/ticket/6682 > > I'll post more about this later. > > BTW a few questions: > > a. is it necessary to put the utf-8 stanza on all files, or only on > those which include non-ascii characters? > > b. the way the line is written, I think it will be recognized by > emacs, but not by vim. Do we care about that? > > c. is there a way to do a "sanity check" to the source to make sure we > don't get incorrect encodings? > > d. should doctests with non-ascii characters be created as unicode > strings, or as regular strings with utf-8 encoding? > > Gonzalo
-- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
