Re: casefold is using unsuitable case mapping table

[Gabriel Krisman Bertazi <krisman@suse.de>]

Björn JACKE <bjacke@SerNet.DE> writes:

> I understand that it's difficult to change this as we store hashes of the
> current lowercase version of the filenames. I'm not an expert enough in the
> filesystem code to come up with a good idea how to solve this though.
> Eventually we can use different versions of casefolding tables and store in the
> filesystem, which version to use?

Regardless of the endless discussion about which code-points to fold or
not fold, which we've been having for years already, we must preserve
existing behavior for existing users, i.e. preserve semantics and disk
names and hashes.  Since the different semantics are a requirement for
SMB, we should envision a way to provide both maps side-by-side.

I suggest we do it as a separate unicode_map that filesystems can opt-in
through a flag in utf8_load.  It should be easy to generate the extra
map and this guarantees we won't break existing users.  I'll can take
look in the next weeks.

-- 
Gabriel Krisman Bertazi