Follow-up Comment #8, bug #65619 (group groff):
[comment #7 comment #7:]
> As a refresher, I'm wondering what should be done about some of the space
glyphs identified in comment #5.
> So, check for "space", "uni0020", and "uni00A0" in that order?
Yes.
> sterlingmonospace;FFE1
This is not a space it's '￡' FULLWIDTH POUND SIGN
> ideographicspace;3000
Yes.
> nbspace;00A0
This is uni00A0 (see above)
> spacehackarabic;0020
Same as uni0020.
> Advice desired.
Attached are three PDFs.
UniSpaces.pdf: Documents any glyph in the unifont.ttf font (which covers
0000-FFFE) where the unicode name includes 'space'. This is a mono-spaced font
so the widths given are not particulary helpful.
TinosSpace.pdf: Similar, but covering the Tinos-Regular.ttf font, which gives
proportional widths (the 4 fields in the first line of each glyph are:
unicode, groff name, width, postscript name).
U-TR: Just showing off my new font tool for a complete font. :-)
My take is that EM SPACE and EN SPACE are too large, and EM divisions would be
unreliable, so I think the glyphs suggested above is what I will use to
calculate 'spacewidth'.
(file #56142, file #56143, file #56144)
_______________________________________________________
Additional Item Attachment:
File name: UniSpaces.pdf Size: 15KiB
<https://file.savannah.gnu.org/file/UniSpaces.pdf?file_id=56142>
File name: U-TR.pdf Size: 415KiB
<https://file.savannah.gnu.org/file/U-TR.pdf?file_id=56143>
File name: TinosSpace.pdf Size: 19KiB
<https://file.savannah.gnu.org/file/TinosSpace.pdf?file_id=56144>
AGPL NOTICE
These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-67b04ef8737d6f02579af43d702ebae34ebfcbfd.tar.gz
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65619>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
