|
Hey guys,
Something performance related: earlier this week (right after I bought my first Kobo), I picked-up on the thread of 'kobofying' epubs (i.e. creating a .kepub.epub file out of an epub inclusive removing 'div' annotations that would spoil the adding of 'span' annotations to the xml that allow the kobo to remember at what page you where at) for 2 reasons: 1) changing pages was very slow with 2.0.0 whilst when using the kepub renderer it was fast and 2) many of my epubs where defined in such a way that they don't react on 'margin-settings' from the kobo-menu whereas with the 'kepub'ed' versions they DO react to margin-settings ..
I came a long way in creating a linux script that would make the changes (thankfully re-using the python/beautifulsoup script that was provided on the forum before) yet since 2.1.1 is available the speed isn't an issue anymore. The difficulty is in creating something thats generic enough to 'understand' the variations (one could also call it 'a mess') in how epubs are structured w.r.t. chapter-naming, split-file-naming, html-directory) etc. so came to the conclusion that this probably wouldn't make it into a flawless automated process .. so I wonder if it makes sense to continue down that path ..
Now my question is about the margin-issue with epubs .. I quickly checked both Sigil and Callibre for options to change margins throughout an ebook but couldn't find it.
Not being an epub/html expert, I expect that there's probably some margin-settings in some epub's that make them 'insensitive' for Kobo's margin-changes from the menu .. but could use some advice/help to tackle this issue (as when solved, I would be happy enough with 'epubs' and dont go after 'kepubbifying' anymore.
Thanks in advance,
Cheers,
hans
|