On Wed, 1 Jun 2011 21:18:15 +0100
Ian Malone wrote:
Yes, in general hours of pain here, especially if you work with
people
who do lots of shell scripting and another group of people who use
Windows lots.
Yea, did anyone notice that Unix/Linux allowed spaces in filenames
for years and years before Microsoft invented NTFS, and no one had
these problems because no one was foolish enough to actually use
spaces in filenames. Then Microsoft was so proud of itself that
they said, "Look everyboy, see what I can do! I'm gonna put spaces
in everything!". It has been going downhill since then :-).
It also broke a lot of stuff even in Windows. I remember finding
all kinds of API documents that claimed an argument was a "filename",
but in reality it was some kind of thing fed to a command somewhere
that needed the so-called filename to be quoted if it had spaces
in it (a minor fact that took years to make it to the documentation
for everything, and may still be missing in some Windows APIs).