Linked by Thom Holwerda on Wed 2nd Dec 2009 23:17 UTC
Features, Office A few weeks ago, we talked about how the rise of computing, a field wherein English is the primary language, is affecting smaller languages, and more specifically, the Dutch language (because that's my native tongue). Of course, it's not just the smaller languages that are affected - English, too, experiences the pressure.
Thread beginning with comment 398016
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Spaces = Silent Reading?
by Doc Pain on Fri 4th Dec 2009 21:46 UTC in reply to "Spaces = Silent Reading?"
Doc Pain
Member since:
2006-10-08

I use Camel Case on my file names because they are easier to read without spaces.


Allthoug spaces are allowed in file names in many file system definitiions, it's obvious that spaces usually are the delimiter character in dialog shells and scripting tools. If file names contain spaces, there's always a need in scripts to include proper quoting, because a space could keep a program from working.

There are other characters that are allowed in file names. You actually *can* use them. But should you?

someFotos of Jim & Bob @ the ``OS" convention "booyah!" in Blödmanntown \ Núßbaumlænd / near Jane's farm[1].JPG

Imagine the fun when you have tons of such file names and you have to script something for them... :-)

As I mentioned before, I prefer the underscore character, even in file names. And I don't use umlauts, eszett ligatures or any possibly special character in them, just [a-zA-Z0-9] and _ - , and #. This has the advantage that file names are readable under any circumstances (no special character map required, no support for UTF-8 needed); this is an essential criterium especially for data recovery needs, where following such a "minimal approach" convention can save you some trouble.

Reply Parent Score: 2