On 2013-07-10, Volker Braun <vbraun.n...@gmail.com> wrote: > ------=_Part_2978_26839636.1373472114217 > Content-Type: text/plain; charset=ISO-8859-1 > > On Wednesday, July 10, 2013 10:27:08 AM UTC-4, Dima Pasechnik wrote: > >> 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. >> > > Do you actually have an example or are you just hypothesizing?
well, it gives me a headache to even think of what happens when one does ssh to a Windows host, running Sage with Cygwin, and how different Cygwin terminals behave wrt UTF-8. Or what happens when one runs a weird ssh implementation on Windows to connect to a Linux host running Sage, which is a common scenario... > TERM > settings and UTF-8 are completely orthogonal issues. In particular, the > UTF-8 bytestream cannot be mis-interpreted as an ansi escape sequence by > dumb terminals, which is one of the reasons for using UTF-8 in the first > place. > -- 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.
