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

[G. Branden Robinson]

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

[comment #34 comment #34:]
> [comment #33 comment #33:]
> > This started off as a simple request to give access to Dingbats
> > glyphs via their \[uXXXX] names... and then wandered!
>
> I agree, the solution you outline will resolve this bug's complaint.  So
taking this out of Need Info.
> 
> It appears that the files you attached all the way back in comment #5 cover
all this.

Quoting this just so to help it reach the top of mind in this epic ticket.

> > The main wandering was the desire to make the grops fonts to
> > be generated during a groff build, and I have given up on that
> > little beauty, although it is 99% doable.

I agree.  I got some ways toward it prior to _groff_ 1.23.0, but got hung up
on the "artifact management" problem.  A bit of work on "maintainer mode" is
required.  My attempt at that is why [this 
https://git.savannah.gnu.org/cgit/groff.git/tree/FOR-RELEASE?h=1.23.0#n12
exists].  It turned out that the X11 fonts were the easiest to deal with.  Too
bad they're by far the least used (well, maybe they beat out _grolbp_).

> That still seems a worthy long-term goal, though, and I'd hate to toss out
the 99%-of-the-way work you've already put in.  But this should definitely be
a separate ticket: It's not necessary in order to resolve the original
problem, as you note.

[comment #35 comment #35:]

> It might even be bug #65698 (which was spawned from Branden's list of tasks
in comment #13).  Or maybe #65698 is merely a prerequisite for generating the
grops fonts?  I don't have much of a handle on what #65698 is asking for.  (I
did open it, but merely parroting Branden's words.)

Rereading my own words, I'm a little fuzzy myself, even after going back down
to comment #13 for context.

I think the idea is that if the font-description-generating tools are
parameterized somehow as constructed in the Git repository, then we need a
process for building them, and that's what #65698 is about: maintainer-mode
targets for updating _afmtodit_, _hpftodit_, and _tfmtodit_ to contain
whatever refreshable information we want to include in them.

That's a separate task, but likely a prerequiste for...
 
> Branden, do I need to open a separate ticket for this?

Yes, for _different_ maintainer-mode targets that produce font descriptions we
check into the repository and ship in distribution archives describing the
"stock" fonts we expect to support for PostScript, LJ4, and DVI output
devices.


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature