View Single Post
Old 06-03-2020, 08:58 AM   #1
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
kepub rendering issue ( i know its a case of GIGO, but...)

so i have a poor quality text with many embedded spans, mid paragraph, like this:
part of paragraph text <span aria-label="page 17" epub:type="pagebreak" id="page_17" role="doc-pagebreak"></span> remainder of paragraph text

in calibre editor, sigil book view, ADE... they are harmless i.e. invisible.

so in fact i never noticed them until I began to read on Forma , and wondered why I was seeing so many "wrong", often mid sentence, paragraph breaks


it seems that on my forma, i get unwanted line breaks whenever such a span is encountered. i.e. the span is interpreted as a <br> , but is otherwise ignored

i am seeing this in a sideload from calibre, so dunno if its the extended driver , building kepub on the fly, that is struggling, or if it would also happen with a proper kepub source. [ the on-the-fly kepub conversion is not retained in calibre , I would have to look up how to capture a copy, in order to dig deeper

I do recall a similar thread ( but cannot find it now) where similar poor coding but with embedded anchors was causing a font size change on kobo.

i can, and did regex it all away, but what should a renderer do with such junk. Why is it NOT a problem on PC, but becomes a mess on Kobo.

is it the epub:type="pagebreak that is doing the damage, or would an embeeded span withonly a page_ID bit also mess up
stumped is offline   Reply With Quote