From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: linux-kernel@vger.kernel.org
Cc: cmadams@hiwaay.net, Willy Tarreau <w@1wt.eu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Helge Hafting <helge.hafting@aitel.hist.no>,
Adrian Bunk <bunk@kernel.org>, "H. Peter Anvin" <hpa@kernel.org>
Subject: Re: [2.6 patch] UTF-8 fixes in comments
Date: Wed, 30 Apr 2008 10:38:32 +0100 [thread overview]
Message-ID: <20080430093831.GD4443@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080430000851.GH4818@implementation>
Chris Adams wrote:
> Once upon a time, Samuel Thibault <samuel.thibault@ens-lyon.org> said:
> >Try init=/bin/sh, from that shell run stty iutf8. Then things will work
> >fine. The fix is thus just to make the VT's tty initial iutf8 setup
> >follow vt.default_utf8.
>
> You may also need to select a UTF-8 locale (e.g. LANG="en_US.UTF-8") for
> programs like bash to handle this correctly.
Yes of course, but here the purpose was _not_ programs like bash, but
the canonical mode (i.e. programs like cat etc.), for which the LANG
variable has no effect, only iutf8 has.
Samuel
next prev parent reply other threads:[~2008-04-30 9:40 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 0:08 [2.6 patch] UTF-8 fixes in comments Samuel Thibault
2008-04-30 3:38 ` Chris Adams
2008-04-30 9:38 ` Samuel Thibault [this message]
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
2008-05-04 10:25 ` Fix VT canonical input in UTF-8 mode [Was: UTF-8 fixes in comments] Samuel Thibault
2008-05-04 11:03 ` Willy Tarreau
2008-05-05 23:00 ` Andrew Morton
2008-05-05 23:54 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
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
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
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=20080430093831.GD4443@implementation.uk.xensource.com \
--to=samuel.thibault@ens-lyon.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=cmadams@hiwaay.net \
--cc=helge.hafting@aitel.hist.no \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.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