MobileRead Forums - View Single Post

davidfor · 06-13-2014, 10:22 PM

I assume the first attempt was simply changing the file name. This triggers the use of the kepub reader, but it isn't enough for the reading position to work. For this, code in the book must include markers that the kepub reader can use for the positions. These are in the form of spans that wrap each sentence in the book. The main purpose of the extended driver is to add these to the epubs and then send them as epubs.

One possible reason is that you didn't remove the original versions. If they had the same file names, the device won't reprocess them and update the internal database with the latest version of the TOC.

Otherwise, it usually means there is an error in the book that prevents the extended driver from adding the spans correctly. I would suggest looking in the extended drivers thread in case there is a suggestion or you can report it there to discuss.

06-13-2014, 10:22 PM	#2
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	I assume the first attempt was simply changing the file name. This triggers the use of the kepub reader, but it isn't enough for the reading position to work. For this, code in the book must include markers that the kepub reader can use for the positions. These are in the form of spans that wrap each sentence in the book. The main purpose of the extended driver is to add these to the epubs and then send them as epubs. One possible reason is that you didn't remove the original versions. If they had the same file names, the device won't reprocess them and update the internal database with the latest version of the TOC. Otherwise, it usually means there is an error in the book that prevents the extended driver from adding the spans correctly. I would suggest looking in the extended drivers thread in case there is a suggestion or you can report it there to discuss.