Quote:
Originally Posted by Gorcsev
Having all my full appreciation for the KTE developer, I would like to ask, is that also a KOBO requirement to flatten the CSS, like calibre does?
I mean the calibre generated classes everywhere, instead of using the p+p, or h+p... approach for handling the paragraphs.
|
I think maybe there is some confusion here. Whether it's mine or yours I'm not sure
Classes being added to every tag, even <i>, <br/> etc, is a function of a full calibre conversion (FROM any format TO any format). This is unavoidable. KTE never does a full conversion to kepub, it only does a format-shift from epub to kepub. If your source epub contains CSS like p+p KTE should leave it there in the kepub transferred to the Kobo. Similarly KTE does not add classes to simple <i>, <br/> tags.
Quote:
Originally Posted by Gorcsev
I simple wanted try out what is better: having long untouched texts or split them.
|
The simplest way to check this out may be to do a temporary hack to your KTE to comment-out adding koboSpans altogether. If you then use KTE to transfer a single epub as kepub you can look at the effect on the text appearance of having long completely untouched texts. If it improves the "look" of your books you would know that it might be worth pursuing the one-per-paragraph koboSpan.
I don't think you would want to leave the "no koboSpans" hack in place as I seem to remember it will remove some of the kepub functionality e.g. highlighting, search in book and also I can't remember what it does to the Kobo's ability to remember book progress between sessions. I think dictionary lookup still works, though.
However, who am I to make that judgement?
If you don't need any of the above, "no koboSpans" is a much easier reliable hack than one-per-paragraph.