Follow-up Comment #9, bug #66323 (group groff): At 2024-10-11T23:01:07-0400, Peter Schaffter wrote: > Follow-up Comment #7, bug #66323 (group groff): > [comment #2 comment #2:] > > Forgot to mention, the problem ultimately could very well lie in the > > formatter, or even in _grops_, but it would be helpful to me if we > > could narrow down what snipped of mom the formatter is handling > > badly, or what sequence of nodes in the output list, or sequence of > > "grout" commands, is sending _grops_ off the rails. > > > > _mom_ is pretty esoteric to me so I'm hoping Peter can aim the > > searchlight. > > With -Tps, the pdf outline and TOC are choking on the ellipsis > character in a string passed to HEADING in the 'bad' file. Remove the > ellipsis and the file processes correctly. Note that the same error > occurs with direct unicode input of special characters and most of the > special character escape sequences listed under "Text markers" in > groff_char(7). \[ps] and \[sc] get a pass for some reason. Whatever > this is, it isn't a mom problem. The arguments mom passes > PDF_BOOKMARK from HEADING are the same for both '\*[.T]'ps' and > '\*[.T]'pdf'.
Got it. This sounds like the "unsanitized section heading"[1] problem,
and an item from my "transparent throughput demystification" checklist
that I hadn't taken care of yet. Namely, even though the grops driver
can't (directly) handle hyperlinks, it needs to handle them similarly to
gropdf, for the exact reason we're seeing here. Deri's already taken
care of the latter but grops is on my plate.
I'll re-assign and re-item group.
Thanks, Peter!
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66323>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
