View Single Post
Old 11-09-2021, 05:35 AM   #4
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
I have had a look, and there is a very simple solution: get a Kobo Sage.

When I downloaded the book, I only had the Sage near me so I put it on that first. It opened with no issues. When I fetched my Libra H2O, it rebooted and was definitely a sickel reboot because it hung.

The issue is basically the size of the ToC. There are over 100005000 entries. When a kepub is first opened, the word count for each internal file is calculated. This is used for progress and the chapter bar charts. It looks like the CPU in the Sage can process the book a lot quicker than the Libra H2O.

As a test, I did reduce the ToC to just the alphabet. That loaded with no problems on the Libra H2O. At 10000+ entries, I don't think the ToC is useful. Maybe if the ToC had a search function, it would be useful, but Kobo does not have that.


Edit: I counted how many times "navPoint" was in the NCX and forgot to halve.

Last edited by davidfor; 11-09-2021 at 05:57 AM.
davidfor is offline   Reply With Quote