On 2013-07-08, Volker Braun <vbraun.n...@gmail.com> wrote: > ------=_Part_5933_16822679.1373249129839 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > Fr=E9d=E9ric Chapoton has written a patch at http://trac.sagemath.org/14733= >=20 > that will beautify the Sage startup banner using some UTF-8 characters to= >=20 > draw the box. This will display incorrectly in terminals that do not=20 > support UTF-8. In that case, Sage still works but the box around the banner= >=20 > is garbled (most likely rendered by placeholder signs for non-ASCII=20 > characters). > > Of course, various Sage source files are already UTF-8 encoded, usually=20 > because of non-ASCII characters in docstrings. These will never render=20 > correctly in ancient terminals, nor will editing such source files lead to= >=20 > much happiness. The questions is essentially, do we want to make it clear= >=20 > to the user right at the beginning that his terminal is not up to the task= >=20 > or would we rather only have more subtle errors later?
ssh from strange terminals often garbles any kind of ascii art, leave alone being UTF-8 clean etc. I've been doing "export TERM=vt100" much too much to trust these things. -1 to the UTF-8 banner, sorry... Dima -- 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.
