Follow-up Comment #5, bug #67971 (group groff): [comment #4 comment #4:] > At 2026-01-29T08:50:30-0500, Deri James wrote: > > I don't now remember, and when I install third-party fonts I always rip > them out again afterwards to keep my test environment "clean". > > So I'll have to stand up an experimental situation again. > > Or some brave volunteer could do so. :) >
Given that Alexis reported problems using the new fonts with -Tpdf, I'd
particularly like to know how you managed to get them to work before you
committed them. I was unable to get them to work with any devices except html
and utf8, where even this works:-
printf ".ft ZR\nハローワールド"| test-groff -Tutf8 -Kutf8 |less
, but it could be just me using it wrong. Which is why I think we need
documentation on usage for each device.
And the new "charset-range" command is telling porkies to troff, since
whatever "real" font is used to get the glyph definitions required for output
is unlikely to have all the glyphs the charset-ranges claimed for the font, so
rather than telling the user:-
[derij@pip build (master)]$ printf ".ft Ryumin\n\[u31F0]"|test-groff -Tpdf -F
~/.groff/fonts -z
troff:<standard input>:2: warning: special character 'u31F0' not defined
You see:-
[derij@pip build (master)]$ printf ".ft JPM\n\[u31F0]"|test-groff -Tpdf -F
~/.groff/fonts -z
The reason is because the JPM groff font says:-
#
# Japanese, Mincho style
# Adobe-Japan1
#
name JPM
internalname Ryumin-Light-UniJIS-UTF16-H
spacewidth 250
charset-range
[...]
u31F0..u31FF 1000 0 --- Katakana Phonetic Extensions
So groff thinks that u31F0 (ㇰ KATAKANA LETTER SMALL KU) is available to use
even if the actual glyph for that character is not contained in the "real"
font. This is new behaviour, previously troff would never 'Cu31F0' if the font
you were using did not contain the glyph. I'm unsure what typesetting output
drivers would do in this case, and since I can't get grops to work at all with
these fonts, I can't investigate!
Waiting for your instructions as to what I have to do to duplicate your
testing.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67971>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
