On Thursday, July 25, 2013 2:05:38 PM UTC-4, Jeroen Demeyer wrote: > On 07/08/2013 04:05 AM, Volker Braun wrote: > > Of course, various Sage source files are already UTF-8 encoded, > Editors like vim for > example can correctly transcode between file and terminal encodings. If > your terminal is iso-8859-1 for example but you're editing a utf-8 file > containing accented vowels, those will display correctly. >
Thats not entirely true either. You can set your editor to dumb it down for the terminal to display, but the editor has no way to find out what the terminal supports. Vim and emacs default to pass-through, letting the terminal deal with whatever is in the source file. Those in the know can then press C-x RET t <encoding> to tell emacs what the terminal supports, but if you know *that* then I'm quite confident that you have switched long ago to a terminal that supports UTF-8. I'm still in favor of using UTF-8 for the banner. So far, the only argument against that has been brought forward is "it looks too nice". I want my punch cards back. Get of my lawn, kids! -- 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.
