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 the
font (u0020 and u00A0) if space is not found, then if none are found, use the
value given on the command line, and if that is missing, it is not a special
font, warn user the font will be unusable in groff and suggest they rerun
afmtodit with a suitable -w flag.
This proposal sounds good to me. *Normally*, I think the Unix command-line
model treats options as overrides rather than fallbacks. But sometimes you
need the latter. Sometimes you need both (witness _preconv_).
So, check for "space", "uni0020", and "uni00A0" in that order?
Hmm, that may be too simple.
There are over 100 matches for "space" in the Adobe Glyph List.
Leaving aside "monospace" names for A-Z, a-z, 0-9, and some other stuff. I
_was_ going to guess the 94 graphical code points, but I see fun stuff like
this too.
sterlingmonospace;FFE1
That ain't ASCII. That ain't ASCII a 'tall.
But with respect to (non-zero-width) spaces, I see:
ideographicspace;3000
nbspace;00A0
There may be others, not sure I got 'em all.
Here's a fun one:
spacehackarabic;0020
NFI if we should deal with that one.
Advice desired.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65619>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
