From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cyd@stupidchicken.com, stepnem@gmail.com, emacs-devel@gnu.org
Subject: Re: tabulated-list-init-header and glyphless-char-display
Date: Sat, 09 Apr 2011 18:37:48 +0300 [thread overview]
Message-ID: <8362qntoz7.fsf@gnu.org> (raw)
In-Reply-To: <jwvei5b8ra8.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Štěpán Němec <stepnem@gmail.com>,
> cyd@stupidchicken.com, emacs-devel@gnu.org
> Date: Sat, 09 Apr 2011 10:56:27 -0300
>
> >> Both characters display fine for me in urxvt and xterm, and even in
> >> the linux console (displayed as up/down arrows instead of triangles)
> >> on a Debian system. Just a data point.
> > That's exactly the _only_ terminal encoding where these characters can
>
> Still, that covers pretty much *all* terminals under GNU/Linux systems.
The world is not limited to GNU/Linux, and even GNU/Linux users might
prefer non-UTF-8 encoding.
> And IIUC the same holds for Mac OS X terminals, so the only significant
> counter example is the Windows terminals (does putty support/encourage
> utf-8?).
Yes PuTTY does support UTF-8. I don't know how to measure
"encourage"; it's not the default, if that's what you are asking. The
default is the current system codepage, which is never UTF-8 on
Windows.
> But your point still holds true: we want/need to properly handle the
> case where the terminal cannot display those chars.
Which is why I don't understand Štěpán's remark at all. It sounded
like he was saying this isn't a problem because it works on GNU/Linux
terminals that use UTF-8.
next prev parent reply other threads:[~2011-04-09 15:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 17:26 tabulated-list-init-header and glyphless-char-display Eli Zaretskii
2011-04-09 10:26 ` Štěpán Němec
2011-04-09 12:12 ` Eli Zaretskii
2011-04-09 13:56 ` Stefan Monnier
2011-04-09 15:37 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-08 17:17 Eli Zaretskii
2011-04-08 18:27 ` Chong Yidong
2011-04-08 18:47 ` Eli Zaretskii
2011-04-08 18:59 ` Eli Zaretskii
2011-04-09 19:26 ` Chong Yidong
2011-04-10 3:59 ` Stefan Monnier
2011-04-10 5:24 ` Eli Zaretskii
2011-04-10 15:47 ` Chong Yidong
2011-04-10 16:53 ` Eli Zaretskii
2011-04-10 18:11 ` Chong Yidong
2011-04-11 17:03 ` Eli Zaretskii
2011-04-11 17:31 ` Chong Yidong
2011-04-11 18:04 ` Eli Zaretskii
2011-04-11 18:39 ` Chong Yidong
2011-04-11 19:27 ` Eli Zaretskii
2011-04-11 22:31 ` Chong Yidong
2011-04-12 3:57 ` Stefan Monnier
2011-04-12 4:51 ` Eli Zaretskii
2011-04-12 5:42 ` Kevin Rodgers
2011-04-12 5:58 ` Eli Zaretskii
2011-04-12 16:12 ` Chong Yidong
2011-04-12 16:45 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8362qntoz7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stepnem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).