View Single Post
Old 09-07-2023, 01:00 PM   #9
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,309
Karma: 105299897
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Quote:
Originally Posted by JSWolf View Post
I'm not sure loading it into a word processor would fix the errors. IMHO, it's easier to fix the ePub.
I agree that normally I'd not export rtf/docx, that I'd edit the epub. But that's ebooks that are bought or from well known PD sites. This looks like a mess. I've occasionally exported/ converted seriously bad azw3 or epub to RTF or docX and then replaced all the body styles, redone headings and special non-chapter breaks etc. Once even stripped back to plain text it was so bad.

Putting it into a word processor never fixes the errors automatically. Manual reformatting the word doc styles in in this case. would help. It's just a less error prone way of making ebooks if you understand paragraph styles. They map 1:1 to CSS and there are never epub errors if a word processor document is done correctly. Of course GIGO applies. A badly done document will give a poor epub, though it will lack most of the errors this example has.

Last edited by Quoth; 09-07-2023 at 01:08 PM.
Quoth is offline   Reply With Quote