Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I guess that's true. I suspect the support for non-UTF8 names in modern tooling is very, very spotty, given how many config files and file formats that refer to other files use UTF-8 themselves. E.g. can you refer to one of these names in an nginx config? (just an example; I have no idea if its config is UTF-8 or not)


I have a collection of non-utf8 and other problematic files to test such tools:

https://github.com/benibela/nasty-files

You probably cannot clone the repo on Windows. It works well on Linux. But in KDE you could not delete it after checkout


Also, filenames with one or more newlines bork a lot of Linux software.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: