Thread: New Kobo Firmware "April 2019" v4.13.12638
View Single Post
Old 04-07-2019, 05:21 AM   #21
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by jackie_w View Post
Can anyone else confirm this problem I'm seeing in 4.13.12638 ...

I'm no longer seeing hyphenation in any of my kepubs. I know I have
-webkit-hyphens:auto
in the body CSS selector of every kepub on my KA1, which is the only device I've installed the new fw on. The same kepubs on my Forma with 4.12.12111 are hyphenating OK.

Hyphenation in epubs still seems to be working OK in the new fw.

I've got quite a lot of patches installed, so it might just be me, but only patches which didn't cause any kepub hyphenation problems in previous fws.
As discussed in PMs, this is being triggered by metadata updates being done by the KoboTouch driver in calibre, and a change in language handling in the firmware. Previously, the firmware wasn't parsing the language from the database when opening the book. Now, it does. Unfortunately, somewhere along the way, Kobo also changed the language code type being used. Before, it was usually the three letter code (ISO 639‑2 or ISO 639‑3). Now, they are using what is basically BCP 47 codes.

The change to fix this is fairly easy in the driver. I am testing it and it will be in the next calibre release. In the meantime, if you are affected by it, turn off the metadata update option in the driver.
davidfor is offline   Reply With Quote