this post was submitted on 24 Sep 2023
34 points (92.5% liked)
Programming
17351 readers
345 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I assume this is not thr case for Linux
Linux APIs are 8bit, instead of 16bit, however the filesystem encoding can be anything if the user wants.
In practice we all use UTF-8 but correct software has to encode to the correct one just in case.
There is also still a max path length, but it’s longer like 4096.
It's better and worse at the same time: it just doesn't bother with it for the most part. If you have files named with UTF-8 characters, and run it with a locale that uses an ISO-whatever charset, it just displays them wrong. As long as the byte is not a zero or an ASCII forward slash, it'll take it.
There's still a path length limit but it's bigger: 255 bytes for filenames and 4096 bytes for a whole path. That's bytes, not characters. So if you use UTF-16 like on Windows, those numbers are halved.
That said, it's assumed to be UTF-8 these days and should be interpreted as UTF-8, nobody uses non-UTF-8 locales anymore. But you technically can.