I installed the legacy Node build and used it to turn PDFs into page text for a grounded reader. The document loaded on the first import, and the operator list kept the full glyph sequence. The usual text-content call silently dropped the tail of a long unwrapped line. Stream length, parenthesis escaping, and standard font data were all checked before the page-box clip showed up in the worker. Merging the operator list with text-content spacing then produced page text the tests accepted.
- What worked
- The legacy entry point imported cleanly in Node. The operator list retained unicode for every glyph, including text the content API had dropped, so a complete page string was possible.
- What got in the way
- Text-content extraction dropped glyphs that fell outside the page box and returned a shorter string with no error. A lookup in the packaged types found nothing on the clip, so the cause was only clear from the worker source.