Follow-up Comment #5, bug #66876 (group groff): [comment #4 comment #4:] > Well, huh, not so hypothetical.
Actually it still is.
> Change (a) is actually pending for _groff_ 1.24.0: the new "charset-range"
> directive invented by TANAKA Takuji for UTF-16-encoded PostScript font
> support is appearing.
TANAKA-san's changes did not impact _afmtodit_; it does not produce the new
"charset-range" directive, and adding support for it would require substantial
new logic: either (1) a new command-line option that took a complex argument,
(2) a new command-line option naming a file from which "charset-range" data is
to be read, or (3) some kind of inference system that synthesized
"charset-range" data for the generated font description file.
(3) seems unnecessarily complex, difficult, and error-prone.
From my armchair, (2) seems like the most likely scenario.
> And I've had plans along the lines of (b).
>
> So. Hmmm.
>
> I guess what we need is a way to make font description file generation
> flexible enough to generate output for "old" _groff_s as well as new ones.
>
> Practically speaking, that means adding a feature to _afmtodit_(1).
>
> This matter will need to be spun off into a new ticket.
But we're not crossing that bridge yet after all.
Also, I haven't forgotten about the original bug report.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66876>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
