MobileRead Forums - View Single Post

aquatic_rent · 05-30-2017, 07:29 AM

Thanks for all your suggestions and help.

For any others that hit this issue:

I did not have errors with tags, calibre's error check didn't show any errors even when I still had this issue. Tag nesting still worth checking to rule things out, could easily cause problems for some.

I'm guessing davidfor's files with nbsp worked because of correct headers.

Some of my embedded html files in the epub had a full header with a DOCTYPE, some didn't, which explains why this behaved inconsistently throughout the book. No idea why my headers were only half correct.

FIX: I used find and replace in Calibre's editor for all instances of nbsp to #160. (You may want a leading ampersand a/o trailing semicolon to avoid false positives.) That was fast, and seems to have fixed it. Double checking the headers of all 30 or so files would probably be the better school solution, but the find/replace was very fast, so if someone else has this issue, I'd try it first.

Thanks again to everyone who weighed in!

(Now how to mark this thread resolved...)

05-30-2017, 07:29 AM	#6
aquatic_rent Junior Member Posts: 5 Karma: 10 Join Date: Jan 2017 Device: Kindle Keyboard 3G (B006)	nbsp not declared Thanks for all your suggestions and help. For any others that hit this issue: I did not have errors with tags, calibre's error check didn't show any errors even when I still had this issue. Tag nesting still worth checking to rule things out, could easily cause problems for some. I'm guessing davidfor's files with nbsp worked because of correct headers. Some of my embedded html files in the epub had a full header with a DOCTYPE, some didn't, which explains why this behaved inconsistently throughout the book. No idea why my headers were only half correct. FIX: I used find and replace in Calibre's editor for all instances of nbsp to #160. (You may want a leading ampersand a/o trailing semicolon to avoid false positives.) That was fast, and seems to have fixed it. Double checking the headers of all 30 or so files would probably be the better school solution, but the find/replace was very fast, so if someone else has this issue, I'd try it first. Thanks again to everyone who weighed in! (Now how to mark this thread resolved...)