Quote:
Originally Posted by jps330
Hit the same ToC bug this week on a daily PDF for reMarkable and Kindle. Two fixes: the go-to links need an indirect reference to the page object, not a page index (pypdf's Link helper quietly writes an index and both devices ignore it), and a PDF outline matters more than in-page links, because Kindle and reMarkable build their contents view from the outline. On full text vs links: I put the editor's own few sentences per story inside the PDF and skip the external links. It sidesteps the copyright worry and reads offline.
|
Thanks! That pinned it down. Turned out I only had half the problem: I build the entries by hand (not through a helper), and they were already indirect refs to the page object rather than an index, so that part was fine. But you're right that it didn't matter, because there was no /Outlines entry at all, just in-page Link annotations on the TOC page.
Kindle and reMarkable apparently don't care how correct your in-page links are if there's nothing in the outline tree for their own Contents view to read.
I've added one bookmark per section, title, Parent/Prev/Next chain, Dest, pointing at the same page refs the in-page links already use, plus PageMode/UseOutlines so it's open by default where that's respected. Looks good on my scribe but I don't have a Remarkable to check it out.
Thanks again