[bug #65619] [afmtodit] want a default value for space width if unspecified

2024-05-03 Thread G. Branden Robinson
Update of bug #65619 (group groff): Assigned to:gbranden => deri ___ Follow-up Comment #5: [comment #3 comment #3:] > A useful change to afmtodit would be to look for other space glyphs in

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

2024-05-03 Thread G. Branden Robinson
Update of bug #63018 (group groff): Status:None => Need Info Assigned to:None => gbranden ___ Follow-up Comment #18: [comment #15 comment

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

2024-05-03 Thread Deri James
Follow-up Comment #17, bug #63018 (group groff): It is a bit moot now. If Branden does have the original afms for the grops fonts, which produce identical meta-data as currently, then much better to run afmtodit on all of them as a refresh.

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

2024-05-03 Thread Dave
Follow-up Comment #16, bug #63018 (group groff): [comment #14 comment #14:] > I'm quite happy to put something in the header like "unicode > names added by Deri 2024", but I certainly would not suggest > removing the afmtodit header which documents the version used, I agree, all metadata

[grog] Certain preprocessors not recognized

2024-05-03 Thread Morten Bo Johansen
Hi Unless I misunderstand something, shouldn't grog detect e.g. a .cstart macro in a document and then come up with a suggestion that includes the "-j" argument for the chem(1) preprocessor? ~/ % echo .cstart | ./grog.pl groff - These do not work either: 'lilypond', 'glilypond',

[bug #64155] [troff] specifying -fZD on command line generates warnings

2024-05-03 Thread Deri James
Follow-up Comment #35, bug #64155 (group groff): [comment #34 comment #34:] > > > Well, when you're prepared to discuss it, it would be good to know if/how Dave's original report in comment #0 was invalid > > > > I think I can answer this - it is certainly not invalid, it just has nothing to do

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

2024-05-03 Thread G. Branden Robinson
Follow-up Comment #15, bug #63018 (group groff): [comment #14 comment #14:] > There is a slight wrinkle with this. Although we have the groff font files for devps, we don't have the original pfa and afm files which were used to generate those files. If we use the current generation of URW fonts,

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

2024-05-03 Thread Deri James
Follow-up Comment #14, bug #63018 (group groff): [comment #9 comment #9:] > Hi Dave, > > [comment #8 comment #8:] > > To clarify: my objection isn't the stale afmtodit version > > It is nevertheless a legitimate one. We should be dogfooding the font description files that _afmtodit_

[bug #64155] [troff] specifying -fZD on command line generates warnings

2024-05-03 Thread G. Branden Robinson
Follow-up Comment #34, bug #64155 (group groff): commit 604361951c9ddad621b3e0786ca7a2946e212842 Author: G. Branden Robinson Date: Fri May 3 00:00:59 2024 -0500 Revert "[troff]: Validate a font family before using it." This reverts commit