Follow-up Comment #4, bug #68923 (group groff): [comment #3 comment #3:] > I think you have an incomplete picture of _groff_'s codebase.
Yes, in much the same way Genghis Khan had an incomplete understanding of
quantum mechanics.
> 2. For every output driver except _gropdf_, the logic that interprets
> these description files is abstracted into static libraries.
>
> 3. The formatter uses those static libraries, too.
So a more accurate Summary for this bug might be "have libgroff and gropdf use
the same glyph-selection method."
> Where there are discrepancies:
>
> A. Either _libgroff.a_ (which has _font.o_ and _fontfile.o_ object
> files bundled into it) is buggy, or _gropdf_ is. (Or both are.)
From Deri's description of the problem, there is no canonically correct
behavior, because with duplicate indices in the font description file, it is
impossible for any algorithm to guarantee it is choosing the correct glyph.
The choice becomes arbitrary, and libgroff made a different arbitrary decision
from gropdf. So while neither one can be deemed buggy, their selecting
different glyphs can be considered, if not exactly a bug, at least a wart.
(Removing the ambiguity from font description files is the provenance of bug
#59402. This ticket has a more modest aim.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68923>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
