On Tue, Feb 07, 2012 at 02:43:19PM +0100, Branko Čibej wrote:
> The client-side mapping table is a more general solution, if a
> lot harder to implement.
> But it brings additional benefits in that we could use it to, e.g.,
> transliterate characters that are allowed by some file systems, but not
> by others; for example, on Unix, file names may contain colons, but they
> can't on Windows. We could even use the mapping table to decorate local
> files that differ only in case on case-insensitive file systems.
These additioanl benefits are great. But to avoid misunderstandings
I'd like to point out that they are of course not required to get
the unicode NFD/NFC problem fixed. In the context of the unicode
NFD/NFC issue, the mapping table exists only to provide backwards
Received on 2012-02-07 15:01:11 CET