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

2024-07-17 Thread Deri James
Follow-up Comment #33, bug #63018 (group groff): Hi Dave, This started off as a simple request to give access to Dingbats glyphs via their \[u] names... and then wandered! The main wandering was the desire to make the grops fonts to be generated during a groff build, and I have given up on t

[bug #66000] [mm] early .CS call makes top page margin wrong thereafter

2024-07-17 Thread Dave
URL: Summary: [mm] early .CS call makes top page margin wrong thereafter Group: GNU roff Submitter: barx Submitted: Wed 17 Jul 2024 10:59:59 AM CDT Category: Macro package mm

[bug #66000] [mm] early .CS call makes top page margin wrong thereafter

2024-07-17 Thread G. Branden Robinson
Follow-up Comment #1, bug #66000 (group groff): Thanks, Dave. And congratulations on the nice round ticket number. Base-10, represent! The margin issue bears investigating. I was planning to add an `AFX` macro to permit override of the formatting of the "affiliated firm" header. Historical pr

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

2024-07-17 Thread Dave
Update of bug #63018 (group groff): Status: Need Info => Confirmed ___ Follow-up Comment #34: [comment #33 comment #33:] > This started off as a simple request to give access to Dingbats > glyp

[bug #66000] [mm] early .CS call makes top page margin wrong thereafter

2024-07-17 Thread Dave
Follow-up Comment #2, bug #66000 (group groff): [comment #1 comment #1:] > Base-10, represent! 1493021! [converted from base 36] (Who's that across the room yelling "NERDS!"?) ___ Reply to this item at:

[bug #66001] [troff] implement saturating arithmetic

2024-07-17 Thread G. Branden Robinson
URL: Summary: [troff] implement saturating arithmetic Group: GNU roff Submitter: gbranden Submitted: Wed 17 Jul 2024 09:47:20 PM UTC Category: Core Severity: 1

[bug #63587] [troff] set .R register to maximum representable integer

2024-07-17 Thread G. Branden Robinson
Update of bug #63587 (group groff): Dependency Removed: => bugs #64301 ___ Reply to this item at: ___ Message

[bug #63587] [troff] set .R register to maximum representable integer

2024-07-17 Thread G. Branden Robinson
Update of bug #63587 (group groff): Depends on: => bugs #66001 ___ Reply to this item at: ___ Message

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

2024-07-17 Thread Dave
Follow-up Comment #35, bug #63018 (group groff): Self-follow-up: [comment #34 comment #34:] > > The main wandering was the desire to make the grops fonts to > > be generated during a groff build, > > But this should definitely be a separate ticket: It might even be bug #65698 (which was spawned

[bug #57506] Suspicious "slant" values in devps/TI, devlbp/HI, devlbp/HBI

2024-07-17 Thread Dave
Follow-up Comment #16, bug #57506 (group groff): [comment #12 comment #12:] > afmtodit has a command-line switch to specify a value for "slant" > different from the .afm file's ItalicAngle. The passage of > afmtodit(1) quoted in comment #6 claims groff uses this value to > adjust diacritic placem

[bug #55154] .tr has undocumented and inconsistent space-character restrictions

2024-07-17 Thread Dave
Follow-up Comment #15, bug #55154 (group groff): [comment #14 comment #14:] > Try this patch: Just tried to apply it, but it appears to have already been committed as [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=84bf4520b commit 84bf4520b].

[bug #55154] .tr has undocumented and inconsistent space-character restrictions

2024-07-17 Thread Dave
Follow-up Comment #16, bug #55154 (group groff): But zooming out: Comment #13 was my attempt to test my hypothesis of "why .char doesn't work for this" as presented in comment #11. This is all tangential to the purpose of this ticket, which covers the .tr request and various types of spaces. Ev

[bug #65108] [troff] support construction of general file name request arguments

2024-07-17 Thread Dave
Follow-up Comment #2, bug #65108 (group groff): [comment #1 comment #1:] > Decide what to do about spaces and tabs. One can argue about tabs > being reasonable in file names, but spaces are a fact of life. > > As it happens, all requests that take _file_ arguments > always do so as the their *la