MobileRead Forums - View Single Post - (Solution) Formatting issues converting from azw3 to epub

SillyStegosaurus · 07-25-2023, 06:58 PM

KindleUnpacked to get an epub.
Opened in Sigil. Selected "no" when it asked if I wanted Sigil to automatically fix defects.
Applied RemoveInlineStyles plugin.
Plugin error: Incorrect XHTML/XML Detected. `Incorrect XHTML: OEBPS/Text/part0000.xhtml Line/Col 18,49 Entity 'nbsp' not declared.`

The Styles/OEBPS/Styles/stylesheet.css is full of this string, "&nbsp", all over the place.

I had it continue anyway to see what would happen. Output:
`Status: success

No inline styles found in: Text/cover_page.xhtml
Removed inline styles from: Text/part0000.xhtml
Inline styles converted to new stylesheet: OEBPS/Styles/sgc_styles.css
`

Saved, hit "no" to "fix on save". Result: Corrupt and unopenable book.
Saved another copy and let it fix on save. Result: Corrupt and unopenable book.

Repeated both of the above, but this time I manually edited all references to the original stylesheet to point to the new stylesheet. Result: Book would open and then Books.app freezes. Or with Calibre's epub reader, the text was still cut off on the left side.

Repeated process but let it do the fix first. Similar results.

Thank you for the help but I think at this point I should just stop burning time trying to get a perfect conversion and go with the good-enough albeit slightly unstyled version I made at the time of my first post. I'd like to know how to fix this properly, but I feel like we're getting into "do a discord call and screenshare to pair program in html" territory.

07-25-2023, 06:58 PM	#12
SillyStegosaurus Member Posts: 19 Karma: 10 Join Date: Feb 2023 Device: Kobo Aura 2	KindleUnpacked to get an epub. Opened in Sigil. Selected "no" when it asked if I wanted Sigil to automatically fix defects. Applied RemoveInlineStyles plugin. Plugin error: Incorrect XHTML/XML Detected. `Incorrect XHTML: OEBPS/Text/part0000.xhtml Line/Col 18,49 Entity 'nbsp' not declared.` The Styles/OEBPS/Styles/stylesheet.css is full of this string, "&nbsp", all over the place. I had it continue anyway to see what would happen. Output: `Status: success No inline styles found in: Text/cover_page.xhtml Removed inline styles from: Text/part0000.xhtml Inline styles converted to new stylesheet: OEBPS/Styles/sgc_styles.css ` Saved, hit "no" to "fix on save". Result: Corrupt and unopenable book. Saved another copy and let it fix on save. Result: Corrupt and unopenable book. Repeated both of the above, but this time I manually edited all references to the original stylesheet to point to the new stylesheet. Result: Book would open and then Books.app freezes. Or with Calibre's epub reader, the text was still cut off on the left side. Repeated process but let it do the fix first. Similar results. Thank you for the help but I think at this point I should just stop burning time trying to get a perfect conversion and go with the good-enough albeit slightly unstyled version I made at the time of my first post. I'd like to know how to fix this properly, but I feel like we're getting into "do a discord call and screenshare to pair program in html" territory.