bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: G. Branden Robinson
Subject: [bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings
Date: Tue, 7 May 2024 05:52:38 -0400 (EDT)

Follow-up Comment #24, bug #63018 (group groff):

Hi Deri & Dave,

[comment #22 comment #22:]
> Speaking about afmtodit only.
> 
> If vintage afm files are not forthcoming, then (2 - makefile target) is
moot.

[comment #23 comment #23:]
> Perhaps, or perhaps it's worth implementing anyway so as to be ready if the
files ever materialize.  Either way, that discussion has little to do with
this ticket's focus (the ZD characters).

In fact I think it's worth considering doing the reverse transformation once,
or writing out own tool to interpret authentic vintage proprietary fonts and
extract their metrics (and other uncopyrightable data), if such metrics files
cannot be located.

We'd then ship those metrics files as part of groff, do the other Makefile
stuff, and no future groff maintainers would have as much difficulty figuring
out these procedures again.

[comment #22 comment #22:]
> Only (1) is not dependent and that will be done when I rejig afmtodit to:-
> 
> Look for different 'spaces' to set 'spacewidth'.
> Implement -ww switch - force even if 'space' found.
> Warn if -w used and 'space' found (but advise rerun with -ww to override).

I ask that we spell these '-w' (fallback) and '-W' (force), respectively.  Or
maybe pick other another letter altogether for one (or both).

Generally, in Unix commands, repeating an option flag, when it is meaningful
at all, means to do something "harder" or "more", not to do it differently.

> Document if -w or -ww used in font header comments.

That's not, in my opinion, strictly coupled to the problem of determining the
space width.  Certainly not a bad thing to do, but it should be a separate
commit.  Oh, and even more so since as Dave points out below, it's a separate
bug report too.

[comment #23 comment #23:]
> (This presumably means bug #65619, as 65659 is for another project.)
> 
> Bug #65619 seems to cover different ground than bug #65697.  Neither one
seems dependent on the other to me, though if I'm wrong, savannah now allows
showing bug dependencies.

Anyway, to reëstablish where _this_ ticket is, it's in "Need Info" state and
assigned to me because I need to figure out if I can use the archive files in
comment #15 with _afmtodit_ to regenerate the _devps_ font description files
we have today.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]