On Wed, 2007-03-14 at 17:44 -0500, Callum Lerwick wrote: > 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... :( This is much more clearer and I agree 101% Simo. -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
