3 ms·
You have the same, if not worse, issue on Linux with filenames that aren’t valid UTF-8 sequences. Not to mention that on Linux switching the locale may change t
by layer8 2y ago
You have the same, if not worse, issue on Linux with filenames that aren’t valid UTF-8 sequences. Not to mention that on Linux switching the locale may change the interpretation of filenames as characters, which isn’t the case with NTFS.
- kwertzzz 2y ago> Not to mention that on Linux switching the locale may change the interpretation of filenames as characters, which isn’t the case with NTFS. If you change the locale to an uninstalled one, then yes. But if the locale is installed, then I don't see a problem. echo $LANG # output: en_US.UTF-8 touch fusée.txt LANG=fr_FR.UTF-8 ls # output: 'fus'$'\303\251''e.txt' sudo locale-gen fr_FR.UTF-8 sudo update-locale LANG=fr_FR.UTF-8 ls # output: fusée.txt Are you maybe using non-UTF-8 locale?
- layer8 2y agoYes, I mean locales like fr_FR.ISO-8859-15, ja_JP.SJIS or zh_CN.GBK. While these probably aren’t used much anymore, it still means that your filenames can break just by setting an environment variable. Or issues like here: https://news.ycombinator.com/item?id=16992546 https://news.ycombinator.com/item?id=16992546