From: Dave Mielke <Dave@mielke.cc>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] have the vt console preserve unicode characters
Date: Wed, 20 Jun 2018 22:21:37 -0400 [thread overview]
Message-ID: <20180621022137.GB18453@beta.private.mielke.cc> (raw)
In-Reply-To: <20180621014317.ebslk3gwvpq3k6sq@angband.pl>
[quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>It's meant for displaying braille to _sighted_ people. And in real world,
>the main [ab]use is a way to show images that won't get corrupted by
>proportional fonts. :-þ
It's not abuse at all. I often use U+28xx to show sighted people what the
braille for something looks like. I often need to do this when, for example, I
need them to comapre what I'm showing them to what's on an actual braille
display. U+28xx is the only way for me to do this without a lengthy description
containing sequences of dot number combinations.
Also, U+28xx is the only reasonable way to share braille music between people
who use different languages.
>The primary users would be:
>* people who want symbols uncorrupted (especially if their language uses a
> non-latin script)
>* CJK people (as discussed below)
Again, that's not true. Why aren't braille users included in this list? After
all, it's we who motivated this enhancement. I guess actual blind people
mustn't count just because there are relatively fewer of us. :-(
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail: Dave@Mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke
Phone: +1 613 726 0014 | Canada K2A 1H7 |
next prev parent reply other threads:[~2018-06-21 2:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 19:07 [PATCH v2 0/4] have the vt console preserve unicode characters Nicolas Pitre
2018-06-17 19:07 ` [PATCH v2 1/4] vt: preserve unicode values corresponding to screen characters Nicolas Pitre
2018-06-17 22:59 ` valdis.kletnieks
2018-06-17 23:17 ` Nicolas Pitre
2018-06-17 23:23 ` valdis.kletnieks
2018-06-17 19:07 ` [PATCH v2 2/4] vt: introduce unicode mode for /dev/vcs Nicolas Pitre
2018-06-17 19:07 ` [PATCH v2 3/4] vt: unicode fallback for scrollback Nicolas Pitre
2018-06-17 19:07 ` [PATCH v2 4/4] vt: coherence validation code for the unicode screen buffer Nicolas Pitre
2018-06-18 22:01 ` Andy Shevchenko
2018-06-19 1:50 ` Nicolas Pitre
2018-06-19 4:52 ` Joe Perches
2018-06-19 12:14 ` Nicolas Pitre
2018-06-19 13:09 ` [PATCH v2 0/4] have the vt console preserve unicode characters Adam Borowski
2018-06-19 13:52 ` Dave Mielke
2018-06-19 15:14 ` Adam Borowski
2018-06-19 15:30 ` Dave Mielke
2018-06-19 15:34 ` Nicolas Pitre
2018-06-21 1:43 ` Adam Borowski
2018-06-21 2:21 ` Dave Mielke [this message]
2018-06-21 3:03 ` Nicolas Pitre
2018-06-22 1:54 ` Adam Borowski
2018-06-22 6:41 ` Samuel Thibault
2018-06-22 15:59 ` Alan Cox
2018-06-22 16:28 ` Nicolas Pitre
2018-06-22 17:51 ` Alan Cox
2018-06-21 2:59 ` Nicolas Pitre
2018-06-25 0:33 ` Adam Borowski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180621022137.GB18453@beta.private.mielke.cc \
--to=dave@mielke.cc \
--cc=gregkh@linuxfoundation.org \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=samuel.thibault@ens-lyon.org \
/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.
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 NNTP newsgroup(s).