View Single Post
Old 09-15-2019, 09:31 AM   #16
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by geek1011 View Post
And I admit kepubify does slightly more then it strictly needs to (but that's about as much extra as it does), but I disagree the HTML cleanup is unnecessary. For cleaning up the HTML, I those fixed were for actual issues I encountered in books, for example self closing title tags, which cause the document to appear empty in stricter parsers such as the one Kobo uses. Note that cleanup doesn't mean beautifying or validating or anything of that sort, which is intrusive
Just being a bit mischievous here ... I'm fairly sure using KTE auto-fixes problems like <title/> purely as a by-product of it using the excellent calibre container functions to read epub and write kepub. It's not necessary to actively run a calibre beautify (pretty_all).

Tags like <title/>, <a id="xxx"/> are auto-expanded and useless (potentially harmful) markup like <i/>, <b/> are auto-removed.
jackie_w is offline   Reply With Quote