Several kobopatch config questions

[jackie_w]

Originally Posted by Antioch

Thank you. I've read the thread and, yes, it seems like I also notice and am annoyed by the div induced spacing issue that is caused by justification + optimizeLegibility. That thread is several years old, however -- has a workaround been developed in recent years?

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.

[Antioch]

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).

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?

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?

[sherman]

Originally Posted by Antioch

Interesting curiosity, but what is the implication?

Was responding to your comment on uneven margins, and that you couldn't see anything in CSS that could cause it. The .xpgt file is a common culprit on older epub files.

Originally Posted by Antioch

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).

Yes it does. It is not aggressive though. The default hyph_xx.dic uses:

LEFTHYPHENMIN 5
RIGHTHYPHENMIN 5

This is one of the things I adjust when I patch my ereaders. My preference is to set both values to 3.

[Antioch]

Originally Posted by sherman

Was responding to your comment on uneven margins, and that you couldn't see anything in CSS that could cause it. The .xpgt file is a common culprit on older epub files.

Ah, understood. I'll keep an eye out for that in the future.

Originally Posted by sherman

Yes it does. It is not aggressive though. The default hyph_xx.dic uses:

LEFTHYPHENMIN 5
RIGHTHYPHENMIN 5

This is one of the things I adjust when I patch my ereaders. My preference is to set both values to 3.

I may have been unlucky, but the first page I loaded after enabling hyphenation had 3 on it which stood out to me (as I don't actively recall seeing hyphenation on my ePubs, though that may be because I'm engrossed in my reading )

Regarding the kerning/ligatures and justification/spacing issues, I wonder if KOReader handles them any better? (Not sure what the advantages of heading down that path would be, however)

[JSWolf]

This is English hyphenation dictionary I use and it works a lot better.

https://www.mobileread.com/forums/sh...d.php?t=252405

[Antioch]

Originally Posted by JSWolf

This is English hyphenation dictionary I use and it works a lot better.

https://www.mobileread.com/forums/sh...d.php?t=252405

Thanks. I saw that and will try. Is OpenOffice's hyphenation dictionary that much better than Kobo's (or Adobe's as the case may be)?

[Deobulakenyo]

Originally Posted by JSWolf

This is English hyphenation dictionary I use and it works a lot better.

https://www.mobileread.com/forums/sh...d.php?t=252405

This will work in fw 4.30 and 4.31, right?