You may not care about putting your non-ASCII name in a file, but others do. As a programmer, you shouldn’t be preventing the user from doing what they want whe

You may not care about putting your non-ASCII name in a file, but others do. As a programmer, you shouldn’t be preventing the user from doing what they want when other software lets them do it just fine. Especially things as simple as file names. You can’t say you’re just solving problems when you ignore the requirements of those problems. Internationalization requires Unicode support. The cat is out of the bag, and if your software doesn’t support Unicode. you’re limiting what your users can do with it. Maybe that’s fine with you and a certain program, but it’s not for a lot of people. You also don’t need to embed full Unicode parsing/support libs if you just treat the user’s input as a byte stream. When programmers try to get fancy and ToUppercase() a byte blob with no regard for what that blob represents - that’s when we have problems.