MobileRead Forums - View Single Post

davidfor · 06-29-2015, 07:54 AM

oren64: As frotschutz implied, you need to send the book to the device as a kepub. For kepubs, a different renderer is used that handles the different language directions better. As a test, rename the book on the device to use the double extension ".kepub.epub". That will trigger the kepub renderer. I downloaded the book you pointed to and did this and, as far as I can tell, it displays and works properly.

Unfortunately, the rename isn't enough except as a proof that it works. You can read the book, but the reading location isn't remembered correctly. The mechanism that kepubs uses for this needs changes to the books. The simplest way to make the changes is with calibre and the KoboTouchExtended driver. This will add the extra code to the books when you send them to the device.

06-29-2015, 07:54 AM	#649
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	oren64: As frotschutz implied, you need to send the book to the device as a kepub. For kepubs, a different renderer is used that handles the different language directions better. As a test, rename the book on the device to use the double extension ".kepub.epub". That will trigger the kepub renderer. I downloaded the book you pointed to and did this and, as far as I can tell, it displays and works properly. Unfortunately, the rename isn't enough except as a proof that it works. You can read the book, but the reading location isn't remembered correctly. The mechanism that kepubs uses for this needs changes to the books. The simplest way to make the changes is with calibre and the KoboTouchExtended driver. This will add the extra code to the books when you send them to the device.