Quote:
Originally Posted by DiapDealer
I'll see what I can see. For what it's worth, the nbsp being changed to #160 when editing in book view is the expected behavior of 0.7.4. The decision to convert non-breaking space characters and named entities to the #160 numeric entity was just about the sole reason for releasing 0.7.4, in fact.
Obviously, the conversion of those #160s to normal spaces when creating a TOC (under certain circumstances) is an unintended side effect. I assume you mean generating the ncx toc rather than an html toc?
|
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
