View Single Post
Old 11-15-2021, 10:24 PM   #5
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 DaveLessnau View Post
It's an old thread, but I just wanted to thank you for the answer. I just had the same issue with a book on my Forma and deleting it from the device and resending it fixed it. Thanks.
And there is an alternative solution. Earlier this year I added a ToC update function to my Kobo Utilities plugin. With that, if you change the ToC or internal file structure, you can send the updated version to the device and then update the ToC. If you have opened the book on the device, it tries to keep the reading position, but, that doesn't always work. It works better for fine-tuning, or where extra chapters have been added than if the ToC is completely rebuilt.
davidfor is offline   Reply With Quote