#18270: Print matrices using unicode large delimiters (on demand)
-------------------------------------+-------------------------------------
Reporter: gagern | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.7
Component: user interface | Resolution:
Keywords: unicode matrix | Merged in:
Authors: Martin von Gagern | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/gagern/MatrixUnicodeDelimiters | e174830facfed57934dec14cf107ffd6952955b5
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Replying to [comment:6 gagern]:
> Replying to [comment:3 vdelecroix]:
> > This banner is already a mess. If I ssh + screen + sage at my
laboratory, …
>
> Perhaps you should file that as a bug, so it can be addressed? Does
using `screen -U` help? What does `locale` print on your client's
terminal, inside the `ssh` and inside `screen` respectively?
Indeed, `screen -U` solves the problem. My locale on the client is
{{{
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
...
}}}
and on the remote is
{{{
LANG=C
LANGUAGE=fr_FR:
LC_CTYPE="C"
...
}}}
> > For the on-demand feature
>
> I meant “on-demand” as opposed to “automatic”, with the demand being
expressed for each matrix that gets printed, i.e. by using the keyword
argument from my commit. I believe you're talking about something far more
automatic here.
>
> > it would be nice to have a global flag allowing (or avoiding) unicode
>
> The canonical way, at least on Linux, would be to inspect `LC_CTYPE`
facet of the current locale, and detect whether that refers to UTF8 or
not. If one used this to automatically choose a sane default, then setting
the `LC_CTYPE` environment variable manually would serve the same function
as the switch you suggest:
>
> {{{
> $ LC_CTYPE=en_US sage # without unicode
> $ LC_CTYPE=en_US.utf8 sage # with unicode
> }}}
>
> Of course, using `en_US` in this example is just the common default. I
guess you as well as I might be using a different setting there in
practice. Adding a switch might still make sense to add visibility to this
feature. But all of this should probably be discussed in a follow-up
ticket once we get the change here accepted.
I like your suggestion very much.
Vincent
--
Ticket URL: <http://trac.sagemath.org/ticket/18270#comment:7>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
