Hi Gonzalo, On Thu, Aug 6, 2009 at 12:21 PM, Gonzalo Tornaria<torna...@math.utexas.edu> wrote: > > On Wed, Aug 5, 2009 at 4:19 PM, <peterjer...@optushome.com.au> wrote: >> >> On 2009-Aug-04 15:49:40 +0100, David Kirkby <david.kir...@onetel.net> wrote: >>>I don't claim to know the most appropiate letter - it was just what it >>>looked like when I see it. But I would agree non-ASCII characters >>>should be removed - it causes many issues. >> >> I would see restricting Sage to ASCII-only as fairly limiting - >> English is one of about two languges that can be expressed using only >> ASCII. If Sage is going to be used (and accept contributions from) >> outside the English-speaking world then non-ASCII support is fairly >> important. >> >> The proposed patch might be the best solution for the short term but >> in the longer term, I believe Sage needs to look at how non-ASCII >> characters can be supported - UTF-8 is probably the best solution here >> since it is a proper superset of ASCII. > > +1 > > My students had very frustrating issues with loading code with > non-ascii characters or CRLF end of lines, just because they use > non-ascii letters in comments or they used an editor with DOS line > endings. > > This arises in the following setup: they write a .py or a .sage file, > which they upload to a sage worksheet. When they try to load the .py, > it gives useless errors if the file contains CRLF or non-ascii > letters. I think it is a bit better when loading .sage files. > > It's especially frustrating since UTF-8 in the notebook works > reasonably well --- can use non-ascii in comments, html cells, even > python strings, etc. (some quirks may remain, but it's pretty good --- > much better than back in march when my course started). > > Also, it'd be nice to be able to spell names properly in sage source > code (this one is way less important to me).
I agree that restricting to ASCII only is a short-term option. The issue that started this thread is related to non-ASCII characters in a patch that modifies sage/graphs/graph.py Because of that patch, it has caused the reference manual to fail to build with Sage 4.1.1.rc1 and resulted in many doctest failures. The issue of non-ASCII characters should be revisited again after the release of Sage 4.1.1. Until then, only ASCII characters should be used in any patches that are to be merged in the 4.1.1 release cycle. -- Regards Minh Van Nguyen --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
