.
Continuation of the original post
https://www.mobileread.com/forums/sh...18#post4487318
because there are a lot of off-topic tangents that might make it difficult to follow the original thread.
— — — — —
I am still trying to make bugs in the KOBO footnotes/endnotes/pop-ups implementation 100% reproducible in order to achieve the best possible consistency in the rendering of epubs on different eReaders (devices and apps).
I performed several hundreds of little changes in order to see how the unstable KOBO reader app on KOBO devices (in my case Clara BW 2024) behaves in different scenarios.
All scenarios were cross checked on iOS on Apple Books, BookFusion and FileBrowser and didn’t produce a single error or inconsistency, except for the KOBO device itself, which appeared to give unpredictable and random results throughout all the tests.
— — — — —
There is one real peculiarity that stands out most, which I will present in the next post after this one to ask your opinion and advice!
— — — — —
This post I just wanna end with a strange general observation that I made along the way.
When
• changing a single character in an epub e.g. the endnote link [1] to [X]
• then zipping the source files and renaming the archive -> only to change the version number (test_01 -> test_02) and the .zip file extension to .kepub.epub
• removing the outdated file (test_01) on the device itself
• sideloading the new file (test_02) to the Clara BW via USB cable
• checking for the correct file name (test_02) on the device with ‘View details…’
the text in the epub is still showing the endnote link as [1] instead as [X].
There seems to be some caching going on on the device that can only be remedied by connecting the device a second time to the host and sideloading the file again.
This of course caused a lot of confusion when doing hundreds of incremental little changes that seemed to act up in unpredictable ways.
With that out of the way here comes the continuation of the thread.
—