On Wednesday, 17 April 2024 21:48:04 BST Alejandro Colomar wrote: > Hi Deri, > > On Wed, Apr 17, 2024 at 09:01:01PM +0100, Deri wrote: > > On Wednesday, 17 April 2024 11:33:58 BST Alejandro Colomar wrote: > > > No, but they contain binary. Here's an example: > > > > > > gropdf:zic.8: warning: Don't understand 'dup 0 11 -| �����B4fD�" |' > > > > Aah, this comes from the new font subsetting code in gropdf. I have not > > seen a font quite like this before, most fonts used with groff have been > > converted from a .ttf/.otf by running it through fontforge.If you are > > interested in the gory details look at the git log for the fix just > > committed to the groff git. > Thanks! However, I can still see that warning. I've installed groff > from git HEAD: > > $ git describe > 1.23.0-1149-g5589bcd18 > $ git log -1 | head > commit 5589bcd18776c6d236c53226a0ee30506180e6b6 > Author: Deri James <deri@xxxxxxxxxxxxxxxxxxxxxx> > Date: Wed Apr 17 19:25:03 2024 +0100 > > Improve font parsing. > > The usual (for fontforge converted ttf fonts) is to use the RD, ND > and NP operators within charstring definitions, however these are > just named in the private subrs dictionary so could be assigned > any name. > > > And here's the warning in the man-pages' contrib branch: > > $ make clean > RM -rf .tmp > $ groff --version | head -n1 > GNU groff version 1.23.0.1149-5589 > $ make build-pdf-book -j24 >/dev/null 2>&1 > $ rm .tmp/man-pages-6.7-63-ga4f3afd28.pdf > $ make build-pdf-book > GROPDF .tmp/man-pages-6.7-63-ga4f3afd28.pdf > troff:fanotify_init.2:322: warning [page 192, 4.2i]: cannot adjust line > troff:membarrier.2:272: warning [page 475, 3.0i]: cannot adjust line > statx.2:240: warning: table wider than line length minus indentation > troff:syscall.2:171: warning: cannot select font 'CW' > troff:syscall.2:301: warning: cannot select font 'CW' > ... > gropdf:zic.8: warning: Don't understand 'dup 0 11 -| �����B4fD�" |' > > > Have a lovely night! > Alex Hi Alex, While testing I used a document just using the debian TinosR font, no problem. Issue occurs when both types of font are used in one document. I have now pushed the fix to groff. Please try again. Cheers Deri
