Document Windows non-ASCII case matching limitation under known issues

This commit is contained in:
Andrea Mazzoleni 2026-08-26 15:17:33 +02:00
parent 4fdfc8a923
commit 0c80cd7dea
42 changed files with 839 additions and 0 deletions

View file

@ -1833,6 +1833,25 @@ Known Issues
Otherwise, the difference will only be detected as a hash mismatch
during a subsequent "scrub" or "check".
Windows non-ASCII case matching
SnapRAID uses standard, predictable UTF-8 encoding across all platforms,
limiting case-insensitive matching to ASCII characters.
Windows filesystems suffer from the legacy design of enforcing case
insensitivity across Unicode filenames via arbitrary, system-dependent
folding tables. Consequently, Windows obscures the reality of the
filesystem by treating completely different Unicode byte sequences as if
they were the same file.
For example, `À.txt` and `à.txt` are distinct Unicode names, yet Windows
illogically treats them as identical, while SnapRAID preserves their true
distinction.
This limitation is caused by Windows's inconsistent handling of Unicode
filenames and its insistence on case-insensitive aliasing. To prevent
discrepancies arising from Windows's case folding, always specify the
exact case for any non-ASCII characters in configuration paths and filters.
Copyright
This file is Copyright (C) 2026 Andrea Mazzoleni