5 ms·
Rendering engines can do anything they want. The question is about source representation only, for semantic purposes. That has nothing to do with output repre
by harshreality 4y ago
Rendering engines can do anything they want. The question is about source representation only, for semantic purposes. That has nothing to do with output representation. Even practicaltypography completely misses that distinction.
You wouldn't publish anything with line breaks between sentences either. Double spacing or line breaks both work nicely for semantic purposes because html (or markdown which almost always ends up displayed somewhere as html) will ignore it.
Any print publishing software in the 21st century should be aware that two spaces in a prose text source is a hint for a sentence break, and treat it appropriately. They often apply custom spacing (slightly more than 1, but nowhere close to 2) between sentences anyway. Without the two spaces, they have to algorithmically guess at sentences. You just won't notice when there are sentence detection errors, unless you're a typography fanatic; who's going to notice 1 space instead of 1.2 or whatever the optimum happens to be?
- sam_bristow 4y agoMaybe I'm just being slow this morning, but isn't the fullstop the indication of the end of the sentence? What extra information is encoded by fullstop + 2 spaces?
- andreareina 4y agoThe period also indicates the previous word was abbreviated, or can be used in an ellipsis, probably other situations that aren't top of mind right now.
- jhardy54 4y agoGP: > Good typography seems to dictate a wider space after a sentence than between words. You: > Rendering engines can do anything they want. The question is about source representation only, for semantic purposes. The thread you’ve commented on is literally about rendering, not source representation and semantics. I agree that you can use a double-space as a sentence delimiter, but we’re currently discussing whether it’s “good typography” to render it that way.
- harshreality 4y agoYour reply cited Butterick which doesn't distinguish the two issues. Every "authority" I've seen strongly admonish against the use of two spaces fails to make this distinction. Which is why I emphasized it. I don't think there's much dispute that two spaces is too much in modern properly rendered prose, so I don't know who "we" is. (And anyone who does think two word spaces is just fine, would probably also agree that it should be configurable and not dependent on two spaces in the source text.) If there's a text renderer out there that renders two spaces as two word spaces in prose, that should be patched, not writers' brains.