View Single Post
Old 08-04-2013, 03:46 PM   #10
user_none
Sigil & calibre developer
user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.
 
user_none's Avatar
 
Posts: 2,487
Karma: 1063785
Join Date: Jan 2009
Location: Florida, USA
Device: Nook STR
Quote:
Originally Posted by PeterT View Post
Seeing an issue in Sigil 7.3 on an ePub that opens correctly ib 7.2.
...
The original ePub when opened via WinZip has the following
...
where the character after pagebreak appears in a hex debugger as hex C2, hex A0.
Most likely it's due to:

"Fix issue 2232: The nbsp characters in UTF-8 files are converted to normal spaces."

What is the doctype set to for the file (opening it outside of Sigil)? The A0 is a non-breaking space which is being converted to   to prevent the bug where it is converted into a normal space. My guess is the doctype isn't correct so it doesn't know what an   is. Hence the not well formed error. The image wouldn't be displayed correctly because the reference was not updated due to the well formed error.
user_none is offline   Reply With Quote