View Single Post
Old 04-13-2019, 08:45 PM   #43
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 gabryele View Post
wait... i'm confused...
I didn't use calibre in this firmware upgrade step.
I noticed the difference with the book that was already uploaded on my Kobo.
Is it still a driver problem?
and when the new version of Calibre will be ready, exactly what command should be used?
There is a change in how the firmware sets and interprets the language code that is stored in the database. The KoboTouch driver has an option to update the metadata in the database. One of the things it does is to set the language code. It does this based on the rules I worked out when I added this option. The driver can update the database on each connection to the device.

The change in the driver is to set the language code based on the current rules. Just connecting the device with the appropriate options set will be enough to fix this with the updated calibre.
Quote:
and... another question:


where is this option?
It is on the third tab of the configuration of the KoboTouch driver, or KoboTouchExtended driver if you use that.
davidfor is offline   Reply With Quote