Aw: Re: German sharp S uppercase mapping

[Marius Spix]

Gesendet: Montag, 2. Dezember 2024 um 14:37
Von: "Dominikus Dittes Scherkl via Unicode" <unicode at corp.unicode.org>
An: unicode at corp.unicode.org
CC: "Dominikus Dittes Scherkl" <lyratelle at gmx.de>
Betreff: Re: German sharp S uppercase mapping
Am 02.12.24 um 14:24 schrieb Julian Bradfield via Unicode:
> On 2024-12-02, Dominikus Dittes Scherkl via Unicode <unicode at corp.unicode.org>
wrote:
>> No. I want to be able if I have 2 files "Weiß.doc" and "Weiss.doc" on my
>> system and copy them to windows, to get 2 files "WEIẞ.DOC" and "WEISS.DOC".
>
> You can't have two files called "Weiss.doc" and "weiss.doc" and expect
> to copy them both to Windows and get two files. Why is this case any worse?
Ok, you are right.
Case-insensitive file-systems simply sucks. No gain in trying to fix them.


The files "weiss.txt" and "weiß.txt" CAN exist on NTFS, VFAT, FAT32, exFAT and ReFS at the same time. For "weiß.txt" an extended filename "WEI~1.TXT" is generated for downward compatibility with software expecting 8.3 filenames.

NTFS and ReFS do support a case-sensitive mode, which is not enabled by default. Even if the case-sensitive mode is off, "weiss.txt" and "weiß.txt" are considered to be distinct files.

However, this won't work with some software like OneDrive or Sharepoint, which do not allow "weiss.txt" and "weiß.txt" in the same directory.

Case-sensitive file systems are supported by the Windows kernel (there is a registry setting called ObCaseInsensitive). This is required for special use cases like GNU on Windows (GOW), but it is not enabled by default, because it would break compatibility legacy software.


</unicode at corp.unicode.org></lyratelle at gmx.de></unicode at corp.unicode.org>