Changes between Initial Version and Version 1 of Ticket #14733, comment 26


Ignore:
Timestamp:
07/08/13 01:48:10 (9 years ago)
Author:
vbraun
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14733, comment 26

    initial v1  
    1 Given that Sage is gravitating towards UTF-8 encoded source files (and, by extension, docstrings), I would argue that it is a feature that we make it immediately and unambiguously clear to the user that his terminal does not support unicode. There is no API to query the terminal whether it is unicode capable, you essentially can only check it by displaying some non-ascii characters. Also, even if you don't have a UTF-8 cabable terminal you can still use Sage, only the banner looks funky.
     1Given that Sage is gravitating towards UTF-8 encoded source files (and, by extension, docstrings), I would argue that it is a feature that we make it immediately and unambiguously clear to the user that his terminal does not support utf8. There is no API to query the terminal whether it is utf8 capable, you essentially can only check it by displaying some non-ascii characters. Also, even if you don't have a UTF-8 capable terminal you can still use Sage, only the banner looks funky.
    22
    33In particular, nobody should be using the following any more at this time: