[bug #58969] [troff] integrate gropdf's foundry concept

[G. Branden Robinson]

Update of bug #58969 (group groff):

                Category:   Font - others/general => Core                   
                 Summary: Request gropdf's foundry concept be integrated into
groff => [troff] integrate gropdf's foundry concept

    _______________________________________________________

Follow-up Comment #2:

Deri recently noted in the first comment to bug #66344, which stumbled back
over this ground.[A]


It would make more sense to add this to groff. So that .ft TR resulted in 'x
font 5 U-TR' if -yU was passed to groff. This would mean no changes to grops,
adding the U- to internalname (by afmtodit), and gropdf dropping the -y flag.
This would mean the download files for grops and gropdf would be same, no
foundry field, the difference would be gropdf would have a download entry for
Times-Roman and U-Times-Roman whereas the grops download would only contain
U-Times-Roman.

The problem with the current system (which I devised!) is that if your
document uses .ft TR and you pass -P-yU you end up with a mongrel, groff using
the meta-data from the TR font but gropdf embedding the font associated with
U-TR, not ideal!

Best not to use '-', Fontnames tend to use it, something like '!' perhaps.
(But lookup place name 'Westward Ho!" [1]  - "there's nowt as queer as
folk").

[1] https://en.wikipedia.org/wiki/Westward_Ho!


[A] We shall not cease from exploration
    And the end of all our exploring
    Will be to arrive where we started
    And know the place for the first time. -- Eliot


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58969>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature