View Single Post
Old 01-01-2014, 12:34 AM   #13
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 29,357
Karma: 211545324
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by theducks View Post
Why would a nbsp be needed in a NCX?
It does not justify.
Not all devices support line wrapping of the NCX TOC so a newline/break is not expected
It's NOT needed.

It's my understanding that the conversions from nbsp to #160 to normal spaces is happening in the html files, not the NCX file. The #160 to normal space substitution is purported to be happening when (re)generating the NCX (and only in those html files where there are new headings to be parsed for the ncx).

I haven't had the opportunity to see if I can duplicate the behavior yet.
DiapDealer is offline   Reply With Quote