Sentence Spacing — 1 Space or 2?
An anonymous reader noted an epic battle is waging, the likes of which has not been seen since we all agreed that tab indenting for code was properly two spaces. He writes "Do you hit the space bar two times between sentences, or only one? I admit, I'm from the typewriter age that hits it twice, but the article has pretty much convinced me to change. My final concern: how will my word processor know the difference between an abbr. and the end of a sentence (so it can stretch the sentence for me)? I don't use a capital letter for certain technical words (even when they start a sentence), making it both harder to programmatically detect a new sentence and more important to do so. What does the Slashdot community think?"
we all agreed that tab indenting for code was properly two spaces
Say what?!?? Who made that decision? In the java world, 4 spaces is pretty standard.
"No matter where you go, there you are." -- Buckaroo Banzai
Well fuck you too, then.
sic transit gloria mundi
It's easier for a human to determine sentence structure when sentences are set apart by two spaces, too.
If your word processor is using the whitespace that you enter, rather than typesetting your text according to whatever your style rules define, you need to get a new word processor. I tend to use two spaces at the end of a sentence, because I tend to edit text in monospace and it gives me a clear visual break between sentences, but that doesn't mean that I expect two spaces in the typeset output - even a web browser is more intelligent than that. Generally I find around 1.2-1.4 gives maximum readability. You want a slightly larger gap between sentences than between words, but double the width of a normal space gives too large a gap for easy reading. Of course, the width of a single space varies slightly from line to line when typesetting justified text.
I am TheRaven on Soylent News
Use LaTeX (especially if you're typing technical things), then you won't have to worry about it. Type what you mean, and let the typesetter and styles handle the details.
(I should note that if have a period followed by space that isn't a new sentence or a or a period following a capital letter that is, in which case you'll need to mark up the period with \ or @ to let it know, but these are generally fringe cases.)
R.Mo
Myself, I'm a two-space typer. My finger know a sentence-ending period is followed by two spaces and they just do it. However, in certain formats, such as HTML, white space is ignored anyway and then formatted by the format-processor (obviously a web browser in the case of HTML).
While I'm a two-spacer, the medium in which we type is largely making this a moot point.
-geis
This diverging discussion is the perfect example of why it is clear the ideal code indentation is a TAB. Set your editor to display whatever indentation width you like, don't expect to inflict that choice on everyone else. Plus it eliminates the possibility of sloppy partial indentations, and it's fewer keystrokes to boot. Win, win, win.
Two spaces makes it easier to parse with a regexp. Any period followed by two spaces is the end of a sentence. If you use one space, you might pick up sentence fragments with titles (Mr. Mrs., etc.)
Of course, the question is really moot. LaTeX ignores whitespace and just does what it thinks is right. I am willing to trust LaTeX.
Give me Classic Slashdot or give me death!
I've been an editor (copy editor, proofreader, senior editor, etc.) for 10 years now. One space.
Why stop there? Really. Is even one space really needed? Doesn't a period, question mark or exclamation point denote the end of a sentence. Why go all redundant and put a space in at all . . .
Oops, I guess an ellipsis can end a sentence too.
I'm not being snarky here. But I am thinking that the answer to the question "Why not zero spaces?" would be "Because that would make it harder to read".
I am not a crackpot.
Probably because html strips out the second space, and slashcode won't recognize  .
Is 1563649 a prime number?