Quote:
Originally Posted by kevin_stevens
Yeah, but that's what bugs me about this "rule". If you look at a book - any typeset book - there is more whitespace after a full stop than after, say, the period in an abbreviation. I don't care what you *call* it, I care what it *does*. If you want to say that double-spacing is the wrong way to create extra space after a double stop - fine. But reality is there is no other easy way to do it in user-generated text. Throwing away the extra space because you don't know how to format it in and double spaces are "wrong" doesn't accomplish anything. And I suspect "wrong" for the standards team really means "a pain to implement".
KeS
(ps - actually, I have one book that *doesn't* have more space after the full stop. It's a geek book on IPSEC implementation, and yes, trying to read it sucks.)
|
It probably goes back to the original block type of the Ben Franklin era with all of the blocks being the same size for uniformity. Of course, the period takes next to no space. IIRC, lead typesetting had different sized 'blocks' for the period, comma, letters "i" and "l", and the number "1".
Unfortunately for you, I don't think we're heading back that way anytime soon.