Follow-up Comment #5, bug #66122 (group groff): One of the changes that was never committed from my deri-gropdf-ng branch was to om.tmac, which removed the calls to pdfmomclean IF using -T pdf, but retained the calls for -T ps. Text in pdfs, such as Author, Title and Bookmarks, can be presented either as PDFDocEncoding (a superset of ISO Latin-1) or UTF-16.
Gropdf can handle being passed \[uXXXX] as text and converts this to UTF-16,
but grops can't, it treats it as plain text. This is why pdfmomclean calls
asciify to convert \[u00E9] back to "'e" which grops handles.
I have attached the relevent changes from my old branch for om.tmac, if Peter
agrees to apply them. I believe Branden is in favour of having all groff input
clean 7 bit ascii and encourage the use of preconv for anything else, so this
patch will stop the warning appearing for pdf output but permit pdfroff to be
used to create mom documents. As a bonus this patch (plus a change to pdfmom
just committed) will now allow mom documents like this:-
.HEADING 1 NAMED Гуляйпольщина "Гуляйпольщина или
Махновщина"
.PDF_LINK Гуляйпольщина PREFIX ( SUFFIX ) "see: +"
Thus allowing mom to be used in many languages (assuming you have suitable
fonts) and take over the world. :-)
There is another of these "transparent device whatchamacallits" when
generating groff-man-pages.pdf (from groff_mmse.7) which can be fixed by
adding "-K utf8" to the pdfmom call in doc/doc.am.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66122>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
