Thanks, this is interesting (and comprehensive). From the above it seems that .EX stuff .EE dropped in the place mentioned will be sufficient to fix this, which of course I'm happy to do. I'll first follow the link and test the proposed fix, this may take between one and a few weeks. If this is inconveniently slow for some reason let me know, then I can be quicker.
Best wishes, Stijn On Sat, Jul 20, 2024 at 7:11 PM Joost van Baal-Ilić <[email protected]> wrote: > Package: aephea > Version: 12-248-3 > Severity: normal > > Hi *, > > When using \verbatim{stuff} or \tt{stuff} in an .azm file, the roff output > features > > .nf \fC > stuff > .fi \fR > > or > > \fC stuff \fP > > . It seems that's not valid roff; lots of details are available from > https://savannah.gnu.org/bugs/index.php?64594 'bug #64594: [troff] > "warning: > cannot select font 'C'"' . Trying to select the 'C' font in roff source > causes > > LC_ALL=C.UTF-8 \ > MANROFFSEQ='' MANWIDTH=80 man --warnings -E UTF-8 -l -Tutf8 \ > -Z man/uruk.8 >/dev/null > > (or just > > groff -t -e -mandoc -Tutf8 man/uruk.8 > > ) to emit > > troff:<standard input>:37: warning: cannot select font 'C' > > ; I've read (also in https://savannah.gnu.org/bugs/index.php?64594 ) it's > better to use > > .EX > stuff > .EE > > I believe changing the code around aephea/mac/aephea/base.zmm , line 118 > > 116 {vq#1} {'\v{\1}'} > 117 {m#1} {\@{\\fC}\1\@{\\fP}} > 118 {tt#1} {\@{\\fC}\1\@{\\fP}} > 119 > 120 {ftinc#2} {\@{\\s+\1}\2\@{\\s-\1}} > > would be one way to fix it. > > I've seen the warning emitted with man-db 2.12.1-2 and groff 1.23.0-5 > (man-db 2.11.2 and groff 1.22.4 do _not_ emit the warning). > > I didn't do all possible testing myself yet. Might get to it, one day. > > Stijn/upstream (Bcc-d): what do you think? > > Bye, > > Joost > >
