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 397635
To read all comments associated with this story, please click here.
Spaces = Silent Reading?
by maxbash on Thu 3rd Dec 2009 04:34 UTC
Member since:

The author lost me in how spaces enabled silent reading. I think the author made that up. I use Camel Case on my file names because they are easier to read without spaces.

Reply Score: 1

RE: Spaces = Silent Reading?
by jack_perry on Thu 3rd Dec 2009 07:11 in reply to "Spaces = Silent Reading?"
jack_perry Member since:

Without entirely agreeing with you, I do think Thom at least implies something wrong when he says, For the first time, reading became something you could do in silence, as a private thing. (emphasis added) Silent reading as a private behavior most definitely existed in Imperial Rome, for example but it was usually done by moving one's lips. Augustine of Hippo, in the Confessions, relates the amazement of him and some friends when they came to meet Ambrose of Milan and found him reading silently. That said, Augustine was a highly educated and cultured man, so this also implies that Thom isn't far off the mark.

On the other hand, Thom is definitely wrong about spaces between words. Spaces don't appear in nearly any writing before the Romans and Greeks (in fact, I can't find any reference to spaces in writing before them). To the contrary, the Romans specifically invented a word divider that everyone else lacked, called the interpunct.

See more fully here:

Reply Parent Score: 4

TemporalBeing Member since:

Further, Greeks did use spacing and punctuation in earlier than the 8th century, and it wasn't added in for the monks - it was added in for people whose second language was Greek. Prior to that there was (i) no spacing, (ii) no sentence punctuation, and (iii) no breathing marks.

Reply Parent Score: 2

RE: Spaces = Silent Reading?
by Doc Pain on Fri 4th Dec 2009 21:46 in reply to "Spaces = Silent Reading?"
Doc Pain Member since:

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