StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The rendering of space characters other than SPACE and NO-BREAK SPACE is not defined in HTML specifications. In practice, various <a href="http://www.cs.tut.fi/~jkorpela/chars/spaces.html" rel="nofollow">fixed-width spaces</a> can be used, and they are not expanded in justification (effectively, they are treated as graphic characters, just with empty glyphs). The one that most closely matches a normal space in width is FOUR-PER-EM SPACE, <code>&#x2005;</code>, but from the comments, it seems that you would rather want to use THIN SPACE or SIX-PER-EM SPACE.</p> <p>Previously, browsers used to treat NO-BREAK SPACE as non-expansible, and some may still do, but for some odd reason, most browsers have abandoned this sensible idea. There is no guarantee that they won’t do the same to fixed-width space.</p> <p>Apart from the theoretical point and the risk mentioned, fixed-width spaces suffer from font problems and breakability. The font problems mainly apply to old versions of IE, and the breakability (i.e., fixed-width spaces are treated as allowing a line break after them) could be addressed by using NARROW NO-BREAK SPACE if its width suits you and you take the risk with the font issue.</p> <p>So it is probably best to do the spacing in CSS, even though it means a bit more work. For e.g. “e.g.” with spacing after the first period, you would need to decide whether it should be “e.g.” or “e. g.” at the character level. In the former case, just wrap the first period in a <code>span</code> and set <code>padding-right</code> on it. In the latter case, you could e.g. use <code>e.<span class=thin>&nbsp;</span>g.</code> and set the width of the <code>span</code> to something sufficiently small (using <code>display: inline-block</code> and a <code>width</code> setting).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload