Quote:
Originally Posted by sherman
I'm afraid not. RMSDK page numbering is basically based on a word/character count, and there's no way to change it.
I'm one of the people who prefer that. It means I know exactly how long a book is, no matter the font size, margins, line spacing etc.
As for the unify font size patch, there's no way to get it pixel perfect. My goal was to get it as close as possible, but the multipliers/divisors I have to work with can only be set in 0.25 increments. Also, as NiLuJe said, kebup and epubs use completely different font renderers.
|
Thank you for the information about the calculations. Also, that is a good point regarding the RMSDK page numbering which I hadn't thought of. I've been using RMSDK exclusively on my Kobo for 8 years now, so I'm used to it, but always notice the irregularity w.r.t. page turns. I wonder if I should continue to ignore it and use ePubs in the future...
Speaking of RMSDK and not noticing things: does it hyphenate by default? I can't say that I remember encountering hyphenations, or they've been rare enough that they don't stand out (compared to the kobo hyphenations with the default dictionary, which feel overly aggressive).
Quote:
Originally Posted by sherman
Just something I've remembered with regards to margins in epub files.
Until recently, it was quite common for commercial epubs to contain RMSDK specific .xpgt stylesheets, which usually contained margin settings. Most other software - including Calibre - does not read these stylesheets. But Kobo ereaders do.
|
Interesting curiosity, but what is the implication?
Quote:
Originally Posted by jackie_w
I'm still using the same workaround (i.e. changing kepub kobospans algorithm) I mentioned towards the end of that thread. It's not guaranteed to reduce occurrences of "weird letter/word-spacing" to zero but I now notice very few at my preferred font-size. Everyone's definition of "weird spacing" varies, of course.
There doesn't appear to be any interest in doing something similar in the official KoboTouchExtended plugin.
|
I'd be interested in trying your algorithm out. Is it implemented in kepubify as an option? Or a fork of KotoTouchExtended on github somewhere?