From: Matthew Wilcox <willy@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: HAN Yuwei <hrx@bupt.moe>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Questions about Unicode Normalization Form
Date: Mon, 8 Apr 2024 04:30:55 +0100 [thread overview]
Message-ID: <ZhNk78RE2Bocs9ap@casper.infradead.org> (raw)
In-Reply-To: <20240408013928.GG13376@mit.edu>
On Sun, Apr 07, 2024 at 09:39:28PM -0400, Theodore Ts'o wrote:
> On Sat, Apr 06, 2024 at 11:15:36PM +0800, HAN Yuwei wrote:
> >
> > Sorry, I am not very familiar with Unicode nor kernel. Correct me if wrong.
> >
> > As to what I have read, kernel seems like using NFD when processing all
> > UTF-8 related string.
> > If fs is using these helper function, then I can be sure kernel is applying
> > NFD to every UTF-8 filenames.
> > But I can't find any references to these helper function on Github mirror,
> > how are they used by fs code?
>
> For the most part, the kernel's file stysem code doesn't do anything
> special for Unicode. The exception is that the ext4 and f2fs file
> systems can have an optional feature which is mostly only used by
> Android systems to support case insensitive lookups. This is called
> the "casefold" feature, which is not enabled by default by most
> desktop or server systems.
As I understand it, an important usecase for the casefold feature is
running Windows games under WINE. I don't do this myself (sgt-puzzles
is more my speed), but there's a pretty important market for this.
Wasn't this why Gabriel was funded to work on it (eg commit b886ee3e778e)?
Or was that the Android usecase?
next prev parent reply other threads:[~2024-04-08 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 9:54 Questions about Unicode Normalization Form HAN Yuwei
2024-04-06 13:26 ` James Bottomley
2024-04-06 15:15 ` HAN Yuwei
2024-04-08 1:39 ` Theodore Ts'o
2024-04-08 1:57 ` HAN Yuwei
2024-04-08 3:30 ` Matthew Wilcox [this message]
2024-04-08 14:15 ` Theodore Ts'o
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=ZhNk78RE2Bocs9ap@casper.infradead.org \
--to=willy@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hrx@bupt.moe \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).