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

2024-04-26 Thread Dave
Follow-up Comment #5, bug #62300 (group groff): [comment #2 comment #2:] > The input sequence '\[u00A0]' is _syntactically_ valid...but > like '\[u]' and '\[u]', it's not _meaningful_ Dear future me: next time you run across this comment and think "I responded to this somewhere" but can't

[bug #63018] font/devps/ZD: make glyphs accessible via their Unicode spellings

2024-04-26 Thread Dave
Follow-up Comment #3, bug #63018 (group groff): [comment #0 original submission:] > defining aliases (probably in tmac/ps.tmac) for \[OK] and \[rh] so > that they can also be represented respectively by \[u2713] \[u261E] On further thought, because these aliases should apply to both the ps and pd

[bug #63018] font/devps/ZD: make glyphs accessible via their Unicode spellings

2024-04-26 Thread G. Branden Robinson
Follow-up Comment #4, bug #63018 (group groff): [comment #3 comment #3:] > On further thought, because these aliases should apply to both the ps and pdf devices, they shouldn't be in a file that only the ps device reads. > > Luckily, the font description file itself includes a mechanism to define