View Single Post
Old 09-04-2013, 12:37 PM   #31
gmw
cacoethes scribendi
gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.
 
gmw's Avatar
 
Posts: 5,818
Karma: 137770742
Join Date: Nov 2010
Location: Australia
Device: Kobo Aura One & H2Ov2, Sony PRS-650
Quote:
Originally Posted by ApK View Post
It doesn't HAVE to just because it's HTML based. I mean, I'm not doubting it does in the app you're using, but HTML does include mechanisms for increasing white space.

In fact, I just tried a straight test in IE 10 and Chrome and they both show the difference between one and two spaces clearly, with no special markup.
Spoiler:
Actually it does, according to the standard. Specified whitespace characters are separators only. CR and LF are also whitespace characters. All whitespace should be consolidated back to represent a single break between words. The behaviour you see in your browsers is definitely non-compliant. Do you see any difference if you place the text inside <p>...</p> ? (Which is how any ebook will present its paragraphs.)

Quote:
Originally Posted by ApK View Post
Then there are <pre> tags, &nbsp, and more.
Yes, there are options, but few are as easy to achieve as a double-tap on the spacebar.

The plugin I use to export from LibreOffice actually converts <space><space> to &nbsp;<space>, but this has it's own problems (upsets justification), so I always remove double-spaces before export.
gmw is offline   Reply With Quote