From: "H. Peter Anvin" <hpa@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Helge Hafting <helge.hafting@aitel.hist.no>,
Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [2.6 patch] UTF-8 fixes in comments
Date: Thu, 01 May 2008 13:18:33 -0700 [thread overview]
Message-ID: <481A2599.4080205@kernel.org> (raw)
In-Reply-To: <20080429230511.GA18377@1wt.eu>
Willy Tarreau wrote:
> On Tue, Apr 29, 2008 at 11:15:54PM +0100, Alan Cox wrote:
>>> OK I could reproduce the case without ever involving either a shell or
>>> readline or anything. Using "cat" as the init program exhibited the
>>> anomaly, though it was not much easy to analyze. Then I switched to
>>> "init=od -An -tx1 -".
>> Did you put the console into utf-8 mode before the cat ?
>
> I had not *explictly* disabled it, since as the doc suggests :
>
> vt.default_utf8=
> [VT]
> Format=<0|1>
> Set system-wide default UTF-8 mode for all tty's.
> Default is 1, i.e. UTF-8 mode is enabled for all
> newly opened terminals.
>
> And I know that I can fix the behaviour by explicitly setting it to zero.
> Also, the fact that "od" shows me multi-byte characters on the input
> indicates to me that everything is set to UTF-8. So unless I'm missing
> something, my console is set by default to UTF-8 (I test this on 2.6.25).
>
Yes, there is apparently a real bug here: this vt setting doesn't
propagate to the tty layer iutf8 flag.
-hpa
next prev parent reply other threads:[~2008-05-01 20:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 15:40 [2.6 patch] UTF-8 fixes in comments Adrian Bunk
2008-04-28 23:05 ` Willy Tarreau
2008-04-29 1:29 ` H. Peter Anvin
2008-04-29 5:06 ` Willy Tarreau
2008-04-29 6:04 ` H. Peter Anvin
2008-04-29 7:29 ` Adrian Bunk
2008-04-29 8:14 ` Willy Tarreau
2008-04-29 9:06 ` Helge Hafting
2008-04-29 9:33 ` Alan Cox
2008-04-29 10:09 ` Willy Tarreau
2008-04-29 10:10 ` Alan Cox
2008-04-29 10:33 ` Willy Tarreau
2008-04-29 10:34 ` Alan Cox
2008-04-29 22:12 ` Willy Tarreau
2008-04-29 22:15 ` Alan Cox
2008-04-29 23:05 ` Willy Tarreau
2008-05-01 20:18 ` H. Peter Anvin [this message]
2008-05-01 9:46 ` Alexander E. Patrakov
2008-04-29 19:33 ` H. Peter Anvin
2008-04-29 10:42 ` Adrian Bunk
2008-04-29 11:06 ` Willy Tarreau
2008-04-29 11:27 ` Adrian Bunk
2008-04-29 11:32 ` Adrian Bunk
2008-04-29 20:18 ` Jeremy Fitzhardinge
2008-04-30 9:15 ` Helge Hafting
2008-04-30 19:22 ` Adrian Bunk
2008-04-30 19:42 ` H. Peter Anvin
2008-04-29 9:43 ` Adrian Bunk
2008-04-29 19:31 ` H. Peter Anvin
2008-04-29 20:05 ` Willy Tarreau
2008-04-29 20:09 ` H. Peter Anvin
2008-05-09 12:48 ` David Kågedal
2008-04-29 9:01 ` Alan Cox
2008-04-29 9:19 ` Jan Engelhardt
2008-04-29 9:34 ` Willy Tarreau
2008-04-29 9:41 ` Alan Cox
2008-04-29 12:18 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2008-04-30 0:08 Samuel Thibault
2008-04-30 3:38 ` Chris Adams
2008-04-30 9:38 ` Samuel Thibault
2008-04-30 19:45 ` Willy Tarreau
2008-04-30 19:49 ` Willy Tarreau
2008-05-03 23:50 ` Samuel Thibault
2008-05-04 8:55 ` Willy Tarreau
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=481A2599.4080205@kernel.org \
--to=hpa@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=w@1wt.eu \
/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