Follow-up Comment #16, bug #67830 (group groff): At 2026-01-26T12:27:50-0500, Deri James wrote: > Follow-up Comment #15, bug #67830 (group groff): > > Most strange!! Two files I attached got uploaded, but not my comments:- > > JPM and CSS are "dummy" fonts, I don't really understand why they were > added to gropdf.
This information is in the "NEWS" file.
NEWS:
* groff now ships font description files usable with the "ps", "html",
"xhtml", and "utf8" output devices to support East Asian fonts.
(Caveat: with few exceptions, groff does not ship font files
themselves.) These are intended as abstractions of faces to permit
consistent naming while allowing custom font selections, just as with
the 12 text typefaces supported across output devices for Latin
scripts in groff (three families of four styles each). These CJK
font descriptions are not organized into groff font families, but are
similarly arranged.
CSH: Simplified Chinese, Hei style
CSS: Simplified Chinese, Song style
CTH: Traditional Chinese, Hei style
CTS: Traditional Chinese, Song style
JPG: Japanese, Gothic style
JPM: Japanese, Mincho style
KOG: Korean, Gothic style
KOM: Korean, Mincho style
Thanks to TANAKA Takuji.
> Even in grops they produce nothing useful,
They should, if the names resolve to fonts you have installed.
> and if you run ghostscript on the postscript file produced you get;-
>
> Warning: glyf overlaps cmap, truncating.
>
> I intend to remove all the dummy fonts from devpdf.
I object. How would you solve problem articulated in "NEWS" instead?
I ask that we avoid having one solution for gropdf and a different one
for grops and grotty, or worse, a different solution for every output
driver.
> However, if you run a slightly modified (see dj-trans.mm) using a real
> installed CJK font (in my case called GR) the results are as expected.
That's the idea. I see your change.
.ftr JPM GR
.ftr CSS GR
...would (should) work just as well. Does that work for you?
What are the CJK equivalents of families "T" and "H"? If they don't
exist already, we have to invent them.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67830>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
