Quote:
Originally Posted by Brett Merkey
It is clear that the last post of Tex2002ans went beyond the call of duty and should be enshrined as the authoritative source on the usage of non-breaking spaces in e-book construction. The Internet Gods will be duly notified.
|
Quote:
Originally Posted by phossler
Agreed
I'm still reading and digesting the last one
His other post and the references also need to be enshrined
|
All my ebook knowledge will be compiled/enshrined on my blog soon* (see my signature).
- - -
* ... eventually... (grumble grumble, two+ years later... where the hell is this time flying?
)
Quote:
Originally Posted by phossler
Now what the Calibre world needs is for a smart PI developer to capture the logic and options since RegEx would seem to be limited
|
Bits and pieces already exist...
But the reason why non-breaking spaces work better in Print is because they have access to:
- Justification at the paragraph level
- Microtypography
- Hyphenation
and you know
exactly where text will land, so you can manually adjust if needed.
Ebooks do:
- Justification at the line level
- have piss-poor support for the various kinds of other spaces
- and the Hyphenation (if it's supported/enabled) is subpar.
This is why it's easier to just use simple normal spaces in nearly all cases.
Adding willynilly all over the place, while it might keep some things together, would lead to horrible tradeoffs elsewhere. (Even making it horrible to read/search/spellcheck your code!)
Side Note: Yes, if the language rules
demand certain spacing (like French with their thin spaced « guillemets »), a in your ebook would be "acceptable"... but tread lightly.