Follow-up Comment #9, bug #66114 (group groff): [comment #5 comment #5:] > Please feel free to improve my documentation (and coding style) :-)
Sure thing. Outside of gropdf.pl I strongly prefer to enforce the
72-character line length limit, so some \newlines may be arriving in
"pdfpic.tmac" soon.
> We need to think about what to put into the NEWS file for all the new pdf
features
I was expecting to base items on what you put together in that
busgrap-generated PDF you first shared last year I think.
There may however be more to say.
> The only place \X'pdf: pdfpic’ is exercised in our documentation is in the
mom examples (typesetting.pdf), but mom does not use .PDFPIC.
That's okay. I think device control escape sequences are little used because
historically they have been hard to understand, and they also have had weird
and frustrating limitations.
> I replaced the sed pipeline with a perl statement, the thinking is that if
the target architecture runs gropdf it must have a perl available and the
statement I used should work on all versions of perl5.
Thanks for being version-conscious. I learned a lot of things about portable
_sed_(1) programming that I wish I'd never had to know. I wrote part of our
"HACKING" file in the blood I spilled from those experiences.
> What I'm less sure about is whether different versions of the programs file,
identify and pdfinfo produce output which is matched with the regex, it may
require tweaking.
It's a hazard. I guess we'll find out! :-O
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66114>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
