|
|
|
|
|
by voussoir
1537 days ago
|
|
Windows user here. I feel that the computer should work for the human, not the other way around. I use whatever unicode characters are appropriate for the file, except the minimum set of disallowed characters: colon, slash, asterisk... Any tool that can't handle that is faulty, and I'll either stop using it or make a temporary symlink to get the job done. But most tools are fine with unicode these days. Of course I speak from the perspective of a personal computer situation with no deadlines or business requirements or software limitations. I still use the old cmd.exe with the Terminal font. It doesn't even render most unicode properly, they come out as ?. I deal with it because I like cmd.exe and I like Terminal and I'd rather see ? than butcher the file's name by romanizing it. |
|