On Monday, July 8, 2013 6:46:40 AM UTC-4, vdelecroix wrote: > If we allow an UTF-8 banner then we may also allow UTF-8 string > representations for Sage objects (why not?).
Kind of off topic, but I think there is no doubt that we will be using UTF-8 for string representations at some point in the future. It would be stupid for a mathematics project to not take advantage of all the mathematical symbol codepoints in unicode. Having said that, it is also true that there are still non-UTF8 capable terminals in the wild. So until we have an idea of how many people are using them, we shouldn't require them to actually use Sage. But the banner and the docstrings aren't really crucial to using Sage. > But I think we do not want to force the user to have UTF-8 output because > it is always harder to parse an UTF-8 string than an ASCII string (this > argument is also valid for the Sage banner). I disagree, the difficulty right now is that you often get a mix of byte strings with various encodings so its not obvious what to do. But Python 3 has only unicode strings, so basically there will be no such thing as an ASCII string. String operations are then naturally unicode and just as easy or difficult as if everything were ASCII. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
