All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] It's UTF-8
Date: Mon, 9 Jan 2006 10:04:48 +0100	[thread overview]
Message-ID: <20060109090448.GA8505@ucw.cz> (raw)
In-Reply-To: <200601082210.09536.s0348365@sms.ed.ac.uk>

On Sun, Jan 08, 2006 at 10:10:09PM +0000, Alistair John Strachan wrote:

> On Sunday 08 January 2006 21:46, Jan Engelhardt wrote:
> > >Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> >
> > I'd say ACK. However,
> >
> > > iocharset=name	Character set to use for converting from Unicode to
> > > 		ASCII.  The default is to do no conversion.  Use
> > >-		iocharset=utf8 for UTF8 translations.  This requires
> > >+		iocharset=utf8 for UTF-8 translations.  This requires
> > > 		CONFIG_NLS_UTF8 to be set in the kernel .config file.
> >
> > If you are really nitpicky about the "-", then it should also be
> > "iocharset=utf-8" (and whereever else). Or what's the real purpose of
> > adding the dashes in only half of the places, then?
> 
> Also what's "Unicode 16" as used in several places in the kernel. Surely this 
> should be changed to UTF-16, which is the _encoding_ for the unicode 
> character space.
 
It might also be UCS-2 and not UTF-16 in some places. They do differ.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2006-01-09  9:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 20:38 [PATCH] It's UTF-8 Alexey Dobriyan
2006-01-08 21:46 ` Jan Engelhardt
2006-01-08 22:09   ` Måns Rullgård
2006-01-08 22:10   ` Alistair John Strachan
2006-01-09  9:04     ` Vojtech Pavlik [this message]
2006-01-08 22:25   ` Alexey Dobriyan
2006-01-09 12:48   ` Kalin KOZHUHAROV
2006-01-09  8:28 ` Alexander E. Patrakov
2006-01-09 11:38   ` Krzysztof Halasa
2006-01-09 18:44     ` Xavier Bestel
2006-01-10  0:12       ` Krzysztof Halasa

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=20060109090448.GA8505@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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.