From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Alexander E. Patrakov" <patrakov@gmail.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] It's UTF-8
Date: Mon, 09 Jan 2006 12:38:07 +0100 [thread overview]
Message-ID: <m3ek3hhbs0.fsf@defiant.localdomain> (raw)
In-Reply-To: <43C21E9D.3070106@gmail.com> (Alexander E. Patrakov's message of "Mon, 09 Jan 2006 13:28:13 +0500")
"Alexander E. Patrakov" <patrakov@gmail.com> writes:
> Alexey Dobriyan wrote:
>
>> if (!strcmp(opts->iocharset, "utf8")) {
>> printk(KERN_ERR "FAT: utf8 is not a recommended IO charset"
>> " for FAT filesystems, filesystem will be case sensitive!\n");
>
> This warning better reads in such a way:
>
> FAT: this is not the recommended filesystem for use with UTF-8 filenames.
>
> Reason: the utf8 IO charset is the only IO charset that displays
> filenames properly in UTF-8 locales. So the choice is really between
> case-sensitive filenames (iocharset=utf8) and completely unreadable
> filenames (everything else).
And UTF-8 locale seems to be the only really sane today. I'd kill the
whole warning.
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-01-09 11:38 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
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 [this message]
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=m3ek3hhbs0.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@gmail.com \
/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).