I figured out how to hyperlink the scanned Table of Contents. I wrote a program, hocrtoc.py <https://github.com/hackerb9/m100manual/blob/main/hocrtoc.py> to automatically convert OCR’d lines into links. (I had thought something like this must already exist, but I couldn’t find it and ended up needing to read the PDF specification.) You can download my latest version from:
https://github.com/hackerb9/m100manual/raw/main/TRS-80_Model_100_Portable_Computer-jbig2.pdf So, now my edition has these differences from Brian’s master copy: - JBIG2 images for much smaller file size, but lower quality images. - Correct metadata. - Correct page labels so that the PDF page numbers correspond to what the book says. - An outline so that one can move through the document quickly from the toolbar. - Annotations on the Table of Contents page so that all entries are hyperlinks. Brian: All my changes, except the JBIG2 compression, should be easily copyable into your archival version using the cpdf command. Things that are still lacking and that I may yet do, time permitting: 1. Add a note on one of the blank inner pages saying something like, “This PDF file has lower quality images to keep the file size reasonable. For the original scan that this is derived from please see https://archive.org/details/trs-80-model-100-portable-computer-owners-manual/” 2. Try hocrtoc on the scanned Index pages at the end of the book to see if they can be converted into hyperlinks. 3. Use ScribeOCR.com to make sure the transcription is completely correct and create an e-book version. 4. Fix up hocrtoc so it can be used for other retro-computing manuals. 5. Once I’m done improving it, stash a backup of the JBIG2 version on archive.org. —b9 On Fri, Jul 17, 2026 at 5:19 AM Brian K. White <[email protected]> wrote: > This is awesome, thank you! > -- > bkw > > > On 7/17/26 07:52, B 9 wrote: > > Thanks for the encouragement! > > > > I’ve learned how to add a PDF document outline and created an updated > > file with an index on the sidebar <https://gist.github.com/ > > hackerb9/4b993d3e204a0eb0e46859a276b22fee/raw/ > > TRS-80_Model_100_Portable_Computer-jbig2.pdf>. > > > > It took a while to type in the outline and page numbers by hand, > > particularly since I added an entry for every BASIC command. I figured > > if I do it right, no one will have to go through this tedium again. The > > outline is structured as a text file (outline.txt <https:// > > gist.github.com/hackerb9/4b993d3e204a0eb0e46859a276b22fee/raw/w- > > outline.txt>) which can be added to the PDF by using |cpdf -add- > > bookmarks outline.txt in.pdf -o out.pdf|. (I don’t know why cpdf > > <https://www.coherentpdf.com/> calls the outline “bookmarks”.) > > > > I still haven’t gotten hyperlinks for the actual text figured out, but I > > noticed cpdf can create a clickable Table of Contents from the outline > > and add it to the beginning of the document. I think it looks a bit ugly > > and may not be so useful since the outline shows on the sidebar anyhow, > > but see this version with a generated TOC <https://gist.github.com/ > > hackerb9/4b993d3e204a0eb0e46859a276b22fee/raw/ > > TRS-80_Model_100_Portable_Computer-jbig2+toc.pdf> for yourself and let > > me know if it's useful or not. > > > > —b9 > > > > > > On Thu, Jul 16, 2026 at 9:41 AM Joshua O'Keefe <[email protected] > > <mailto:[email protected]>> wrote: > > > >> On Jul 16, 2026, at 8:56 AM, B 9 <[email protected] > >> <mailto:[email protected]>> wrote: > >> > >> I’ve created amuch smaller version of the PDF <https:// > >> gist.github.com/hackerb9/4b993d3e204a0eb0e46859a276b22fee/ > >> raw/59f26ba22962e78005fee4ee18fec42bdab570e0/ > >> TRS-80_Model_100_Portable_Computer-jbig2.pdf>(40 MB instead of 2 > >> GB) by using JBIG2 symbol compression. > > > > Within the limits of what jbig2 can do, this is a delightful > > tradeoff of readability for size. Great work! As a daily driver > > version of the manual it seems far more than adequate given that > > it's about the size of a baby's pinky nail. > > > > I'd love to see all the variants people are working on consolidated > > into a single collection once the dust settles. No doubt those who > > come after us would benefit from scrounging all over the internet > > hunting down which copy is which, or losing track of the reference > > scan. We already run into this problem today with slightly divergent > > copies of the same document becoming "welp, that's all we've got." > > > > Thanks for offering this up! > > > > > -- > bkw >
