UTF-8 and filenames

Callum Lerwick seg at haxxed.com
Wed Mar 14 22:44:11 UTC 2007


Okay, so people missed my point.

The point is, if its a tool that doesn't *have* to care about encodings,
then it should not care about encodings. If its not something that
performs stuff like alphabetical sorting or case insensitive comparison,
then it should just accept and pass on the filename as a bag of bits,
not caring what they mean.

For example, for a long time rsync wouldn't allow you to specify files
and directories with spaces in the name on the command line, no matter
how hard you tried to escape or quote it. It would interpret the space
as a filename seperator. This finally got fixed at some point though. :)

This also applies to people not properly quoting variables in shell
scripts... :(
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-maintainers/attachments/20070314/1dfbf6ce/attachment.sig>


More information about the Fedora-maintainers mailing list