On Sat, Jan 23, 2021 at 11:59:12PM +1100, Chris Angelico wrote:
So Windows is being a pain in the behind, once again, because it doesn't move forward.
*cough* That would be called "backwards compatibility" :-) Microsoft's attitude towards backwards compatibility is probably even stricter than ours.
File names on Mac OS and most Linux systems will be in UTF-8, regardless of your chosen language. Why stick to other encodings as the default?
Aren't we talking about the file *contents*, not the file names? The file name depends on the file system, not the OS. On Mac OS, the file system used until High Sierra was HFS+, where file names are UTF-16. I expect that there will still be many Mac systems with HFS+ file systems. After High Sierra, the default file system shifted to APFS which does use UTF-8. Linux file systems such as ext4 are bytes. Any UTF-8 support is enforced by the desktop manager or shell, not the file system, and so can be subverted, either deliberately or accidently (mojibake). -- Steve