It's hard to sufficiently emphasize how ugly this looks in an Emacs shell
buffer. I use the Inconsolata font with emacs, and it doesn't have those
characters (the dashes and corner characters), so Emacs goes to a different
fixed-width font for them, and that font has a different width, so the
William Stein wst...@gmail.com writes:
Also, UTF is clearly the future of strings, having native default
support in modern interpreters, editors, etc., and also being critical
to supporting users who aren't using English.
Maybe one day Sage will support something like agda-input-method in
Its always hard to please everybody, We haven't really reached any
consensus, nor does it sound like there is much to be gained by further
discussion. So i'll set the ticket to positive review and leave you with
Lichtenberg's aphorism:
Ich weiss nicht, ob es besser wird, wenn es anders wird.
At the very least, lets be careful to avoid fancy invisible unicode
characters: https://groups.google.com/forum/#!topic/sage-devel/LjC75cae7XI
On Thu, Jul 25, 2013 at 9:52 PM, William Stein wst...@gmail.com wrote:
On Mon, Jul 8, 2013 at 2:05 PM, Robert Bradshaw
rober...@math.washington.edu
Although (perhaps?) surprising, some languages don't have spaces and
require zero-width space to designate word boundaries for line breaks.
On Friday, July 26, 2013 3:02:41 PM UTC-4, Robert Bradshaw wrote:
At the very least, lets be careful to avoid fancy invisible unicode
characters:
On Mon, Jul 8, 2013 at 2:05 PM, Robert Bradshaw
rober...@math.washington.edu wrote:
On Mon, Jul 8, 2013 at 1:55 AM, Julien Puydt julien.pu...@laposte.net
wrote:
Le 08/07/2013 10:51, Nils Bruin a écrit :
On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote:
Frédéric Chapoton has
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
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
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
Since evidently nobody who weighted in so far has actually tried the patch,
here are screenshots of a few different terminals:
http://boxen.math.washington.edu/home/vbraun/UTF8/
In particular, Putty works beautifully if you set it to UTF-8. And if you
don't then you can still use Sage just
On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote:
Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733that
will beautify the Sage startup banner using some UTF-8 characters to
draw the box. This will display incorrectly in terminals that do not
support UTF-8.
Le 08/07/2013 10:51, Nils Bruin a écrit :
On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote:
Frédéric Chapoton has written a patch at
http://trac.sagemath.org/14733 http://trac.sagemath.org/14733 that
will beautify the Sage startup banner using some UTF-8 characters to
Le 08/07/2013 10:51, Nils Bruin a écrit :
On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote:
Frédéric Chapoton has written a patch at
http://trac.sagemath.org/14733 http://trac.sagemath.org/14733 that
will beautify the Sage startup banner using some UTF-8 characters to
IIRC the new GAP banner uses UTF-8.
On Monday, July 8, 2013 11:28:23 AM UTC+2, tdumont wrote:
Le 08/07/2013 10:51, Nils Bruin a �crit :
On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote:
Fr�d�ric Chapoton has written a patch at
http://trac.sagemath.org/14733
On Monday, July 8, 2013 11:33:18 AM UTC+2, Jean-Pierre Flori wrote:
IIRC the new GAP banner uses UTF-8.
You're right. With (to me) the same jarring effect, so I don't like it.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe
If we allow an UTF-8 banner then we may also allow UTF-8 string
representations for Sage objects (why not?). 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
On Monday, July 8, 2013 12:46:42 PM UTC+2, Nils Bruin wrote:
On Monday, July 8, 2013 11:33:18 AM UTC+2, Jean-Pierre Flori wrote:
IIRC the new GAP banner uses UTF-8.
You're right. With (to me) the same jarring effect, so I don't like it.
That was also a problem to me when I updated
On Monday, July 8, 2013 4:51:28 AM UTC-4, Nils Bruin wrote:
all the colour stuff should shut off automatically for a dumb terminal).
The colors are ansi escape sequences, they have nothing to do with unicode
for the record
Why require it for *just* the banner?
As I said already, we
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
On Mon, Jul 8, 2013 at 1:55 AM, Julien Puydt julien.pu...@laposte.netwrote:
Le 08/07/2013 10:51, Nils Bruin a écrit :
On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote:
Frédéric Chapoton has written a patch at
http://trac.sagemath.org/14733
20 matches
Mail list logo
