Earlier quoted context omitted.
Exactly. "I live in the U.S. I am happy." requires a bit more cognitive work to parse if spaces after sentence-ending periods are not wider. EDIT: For completeness, here is that same text with an extra space: "I live in the U.S. I am happy." -- see how much easier that is to read? Sure, it's not that big a deal, but it's definitely kind to the reader.
Regarding your edit, it appears exactly the same :(. The browser collapses whitespace. I'm not sure if HN's comment system will allow you to double-space after a period, other than in a block: I live in the U.S. I am happy. I live in the U.S. I am happy.
Regarding the Em Dash
191–200 of 219 posts
Re: Regarding the Em Dash
#192Earlier quoted context omitted.
Exactly. "I live in the U.S. I am happy." requires a bit more cognitive work to parse if spaces after sentence-ending periods are not wider. EDIT: For completeness, here is that same text with an extra space: "I live in the U.S. I am happy." -- see how much easier that is to read? Sure, it's not that big a deal, but it's definitely kind to the reader.
British: I don't live in the US. I am happy. Full stops aren't generally used in abbreviations here, Mx Cryptonector. Though there's a more recent trend to write "Nato" rather than NATO, which annoys me for the inconsistency that arises. Plenty of people pronounce VAT as one word, or PAYE, but these are usually left in capitals.
Re: Regarding the Em Dash
#193Earlier quoted context omitted.
I like sticking to ASCII when I stick to English. (Of course, when I write in other languages, I use UTF-8.)
That doesn't work outside America, where accents are often retained (café, façade, naïve) and £ or € is often needed.
Re: Regarding the Em Dash
#194Earlier quoted context omitted.
I like sticking to ASCII when I stick to English. (Of course, when I write in other languages, I use UTF-8.)
Here in New Mexico ñ is very common in place names. And I’ve known people with accented names who, though they don’t insist on it, appreciate (sometimes visibly brightening) when their names are spelled accurately.
Re: Regarding the Em Dash
#195Yes! I use em dashes quite often. I tire of commas and parenthesis. I do prefer two short dashes together, because I enjoy ASCII. I also use short dashes as parenthesis sometimes, -like this-, but this doesn't always work well as some UIs use that for strikethrough. EDIT: Do please put whitespace around em dashes.
To your edit: i wouldn't recommend, the EM dash should generally be used without surrounding spaces. It is dimensioned to set a proper pause in the text and will rip holes in your text body if surrounded by so much additional white space. You also wouldn't put a space before a period . (Use an EN dash with spaces, if you must)
Re: Regarding the Em Dash
#196Earlier quoted context omitted.
There may not be rules but there are conventions. These conventions are rarely very strict but they do help communicate your ideas. Understanding them and understanding the impact of not using them is an important set of knowledge if you want to be clear and well understood in your writing. It is similar to good typography in that it isn't required but that it will often make the reader enjoy or understand the work m…
You're saying only the qualified are allowed to break conventions you were taught. You are free to follow that; I am free to not.
You are free to break whatever convention you like. It will just effect your communication clarity.
Understanding that (and how and why too) will help you be more effective.
It’s no different to saying “you can program it that way if you want but understanding the conventions & methods other people use may help you have more readable and efficient code”.
Re: Regarding the Em Dash
#197I've been abusing the em dash since.
Re: Regarding the Em Dash
#198Earlier quoted context omitted.
> While we're on this subject, wide spacing between sentence-ending periods and the next sentence is the Right Way (tm). This convention started with typewriters, and typesetters (e.g. my parents) will tell you that it is only considered correct in monospace fonts. This is also why HTML takes the liberty of reducing whitespace down to a single space character unless you go out of your way to use an .
> typesetters (e.g. my parents) will tell you that it is only considered correct in monospace fonts People like to say that but it's never been explained to my satisfaction. Spaces are twice as wide in a monospace font. Why would you use more spaces when and only when you have a longer space?
I've also wondered this. Referring to this mock-up[1], I have the same monospace text with single vs double spaces after sentences, and proportional font with single vs double. The usual argument is that #2 is better than #1 (for mono), but #3 is better than #4 (for proportional). It feels like an inconsistency in the preference, and (as you pointed out) the reasoning doesn't make sense.
Re: Regarding the Em Dash
#199Earlier quoted context omitted.
The space is conventional in Britain. Without the space looks strange to me. (Android users — try long pressing the - key in the punctuation menu.)
In my opinion — and let's face it, much of this is just a matter of opinion! — a normal space is too much. Try thin space (U+2009) for a more subtle effect. (The exact result may depend on your font, however.)