View Single Post
Old 05-13-2013, 02:24 PM   #22
BobC
Guru
BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.BobC ought to be getting tired of karma fortunes by now.
 
Posts: 691
Karma: 3026110
Join Date: Dec 2008
Location: Lancashire, U.K.
Device: BeBook 1, BeBook Pure, Kobo Glo, (and HD),Energy Sistem EReader Pro +
I see similar to roger64. I had a look at writer2xthml and it is quite out of date and only in beta anyway so I took your text and re-created it using LibreOffice 4 with the Writer2Epub extension but with a few spaces changed to what LO uses for non-breaking spaces (control-shift-space).

When I looked at the epub file generated all the non-breaking spaces from the odt document had disappeared and there was only one present - a placeholder in a blank line :

Code:
<p>&nbsp;</p>
not something I intended but clearly something that the conversion had inserted. At least it proved that if there had been proper html &nbsp; entities where I had put them they would have been visible.

HOWEVER where I had a non-breaking space in the original it had A000 rather than 2000 as the hex value in the output.

So I then re-examined your test document and found the same - all the non-breaking spaces are coded as A000 rather than as an HTML entity.

It appears the "deprecated" Sigil would convert the A000 to &nbsp; whereas 7.2 doesn't.

BobC

Last edited by BobC; 05-13-2013 at 02:27 PM. Reason: Subject and object must agree in number.
BobC is offline   Reply With Quote