From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Dave Mielke <Dave@mielke.cc>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] have the vt console preserve unicode characters
Date: Fri, 22 Jun 2018 08:41:46 +0200 [thread overview]
Message-ID: <20180622064146.7x6dh7hruidjgtag@var.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <20180622015445.7r5u5nn6ofhd4k57@angband.pl>
Adam Borowski, le ven. 22 juin 2018 03:54:45 +0200, a ecrit:
> if the former, this is my way to show you how actual Latin letters
> look like, without a lengthy description of letter shapes. :) )
What will unfortunately not work: braille displays only show one line at
a time, so they can't show the global shape of a figure, unless it is
only 4pixels tall.
Samuel
next prev parent reply other threads:[~2018-06-22 6:41 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
2018-06-21 3:03 ` Nicolas Pitre
2018-06-22 1:54 ` Adam Borowski
2018-06-22 6:41 ` Samuel Thibault [this message]
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=20180622064146.7x6dh7hruidjgtag@var.youpi.perso.aquilenet.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=Dave@mielke.cc \
--cc=gregkh@linuxfoundation.org \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.