Thread: [GUI Plugin] Modify ePub
View Single Post
Old 10-10-2019, 06:58 PM   #1292
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by JSWolf View Post
I found what may be a bug. An ePub that is not a KePub is showing that Kobo Spans have been stripped.

Can you have a look and see why this is happening and what it's actually doing? I've attached a scrambled version of the eBook that's showing this behavior.
In this case, it looks like the HR element is getting checked and processed without actually being changed. That's part of a safety check to guard against unclosed BR and HR elements.

It's not strictly a Kobo issue, and the same logic appears in the generic "strip spans" routine as well. I don't recall why it's in both places; perhaps I saw the issue in some Kobo books and put the logic there for extra security (in case the user didn't also have strip_spans checked).

Bottom line: it doesn't hurt anything, it's not changing the code in this specific case (aside from some spacing that doesn't affect anything), and thus it's more of a circumstantial oddity than a bug.
Rev. Bob is offline   Reply With Quote