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

Follow-up Comment #23, bug #63018 (group groff): Don't read too much into my opening multiple tickets: they're not saying "THESE THINGS MUST BE DONE" but giving venues to consider and discuss separate issues without cluttering this bug. At least that was the theory. ;-} Any ticket can be closed

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

Follow-up Comment #22, bug #63018 (group groff): Speaking about afmtodit only. If vintage afm files are not forthcoming, then (2 - makefile target) is moot. Only (1) is not dependent and that will be done when I rejig afmtodit to:- Look for different 'spaces' to set 'spacewidth'. Implement -ww

[bug #65702] tmac/doc.tmac: previous state of compatibility (register '.cp') is not restored at end

Update of bug #65702 (group groff): Status:None => Need Info ___ Follow-up Comment #1: This situation dates back to primordial groff. The current .cp line was introduced in the 2001

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

Follow-up Comment #21, bug #63018 (group groff): True for the third ticket of that trio, but the first two can be implemented regardless of the fate of the old AFM files. As for the third, it documents a different issue from this ticket and should have its own venue, so that when this ticket is

[bug #65702] tmac/doc.tmac: previous state of compatibility (register '.cp') is not restored at end

URL: Summary: tmac/doc.tmac: previous state of compatibility (register '.cp') is not restored at end Group: GNU roff Submitter: bjarniig Submitted: Mon 06 May 2024 08:36:27 PM UTC

[bug #65701] tmac/doc.tmac: extra '.ec'

URL: Summary: tmac/doc.tmac: extra '.ec' Group: GNU roff Submitter: bjarniig Submitted: Mon 06 May 2024 08:25:51 PM UTC Category: Macro package mdoc Severity:

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

Follow-up Comment #20, bug #63018 (group groff): This might be a bit previous! Whether we should regenerate the grops font files is rather dependent on whether Branden is successful in locating afm files of a suitable vintage so that running current afmtodit will generate fonts with compatible

[bug #57506] Suspicious "slant" values in devps/TI, devlbp/HI, devlbp/HBI

Follow-up Comment #15, bug #57506 (group groff): [comment #2 comment #2:] > It seems to me that these files should be regenerated, if not > on every build, then at least for every release. Now bug #65699. ___ Reply to this item at:

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

Follow-up Comment #19, bug #63018 (group groff): [comment #13 comment #13:] > In fact I see two issues springing thence. So, to summarize. > > 1. Make comment headers of font description files we generate > with tools more informative. Now bug #65697. > 2. Add "maintainer-font-descriptions"

[bug #65699] Update the procedure documented in "FOR-RELEASE"

Update of bug #65699 (group groff): Depends on: => bugs #65698 ___ Reply to this item at: ___ Message

[bug #65699] Update the procedure documented in "FOR-RELEASE"

URL: Summary: Update the procedure documented in "FOR-RELEASE" Group: GNU roff Submitter: barx Submitted: Mon 06 May 2024 11:18:05 AM CDT Category: Utilities

[bug #65698] Add "maintainer-font-descriptions" make(1) targets for *todit utilities

URL: Summary: Add "maintainer-font-descriptions" make(1) targets for *todit utilities Group: GNU roff Submitter: barx Submitted: Mon 06 May 2024 11:12:29 AM CDT Category:

[bug #65697] Add info to comment headers of font description files groff tools generate

URL: Summary: Add info to comment headers of font description files groff tools generate Group: GNU roff Submitter: barx Submitted: Mon 06 May 2024 11:03:53 AM CDT Category:

[bug #65585] [gropdf] problems introduced by commit cd9fde325f

Update of bug #65585 (group groff): Status: Need Info => Fixed ___ Follow-up Comment #9: commit a951b44fd9d2acf060067b24c994604351a27888 Author: Deri James Date: Tue Apr 30 15:25:49

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #9, bug #62300 (group groff): [comment #7 comment #7:] > if the above is in fact the case, one of us should open a new bug report. Bug #65693 ___ Reply to this item at:

[bug #65693] exceptions to NBSP statement in groff_char(7) should be documented

URL: Summary: exceptions to NBSP statement in groff_char(7) should be documented Group: GNU roff Submitter: barx Submitted: Mon 06 May 2024 02:06:11 AM CDT Category: Core