[bug #64484] [troff] .device and \X don't behave the same

Update of bug#64484 (group groff): Status:None => In Progress ___ Reply to this item at: ___ Message s

[bug #64071] [troff] support construction of proper C strings for request arguments destined for the shell or file system

Follow-up Comment #1, bug#64071 (group groff): I'm thinking the way to do this is: 1. Add a function much like input.cpp's `encode_char_for_troff_output()` (as it is named in a pending push), `encode_char_for_system_output()`. 2. Have this function encode output much as the foregoing does. Th

[bug #65077] [ms] unexpected suppression of `sp` effect after `DE` call

Update of bug#65077 (group groff): Assigned to:gbranden => None ___ Follow-up Comment #2: Unassigning from self--"Need Info" status is waiting on submitter, not me.

[bug #64994] math.h fails to compile on macOS 19 because it does not include config.h

Update of bug#64994 (group groff): Assigned to:gbranden => None ___ Follow-up Comment #5: Unassigning from self--"Need Info" status is waiting on submitter, not me.

[bug #64910] build failure with clang++ on z/OS (include assert.h _after_ config.h)

Update of bug#64910 (group groff): Assigned to:gbranden => None ___ Follow-up Comment #5: Unassigning from self--"Need Info" status is waiting on submitter, not me.

[bug #64728] diversion widths reported when using eqn mark/lineup feature inconsistent with Heirloom

Update of bug#64728 (group groff): Assigned to:gbranden => None ___ Follow-up Comment #6: The information needed here is a gathering of information about various *roff implementations. This

[bug #64529] [ms] confusing diagnostics when starting document with blank line or `KF` call

Update of bug#64529 (group groff): Assigned to:gbranden => None ___ Follow-up Comment #2: Unassigning from self--"Need Info" status is waiting on submitter (or the general public), not me.

[bug #64285] [troff] \D't' (set line thickness) drawing command alters drawing position

Update of bug#64285 (group groff): Assigned to:gbranden => deri ___ Follow-up Comment #10: I see very little difference between PS and PDF output for your input exhibit in comment #9, using b

[bug #64484] [troff] .device and \X don't behave the same

Update of bug#64484 (group groff): Severity: 2 - Minor => 3 - Normal Item Group: Incorrect behaviour => Feature change Status: In Progress => Fixed Open/Closed:

[bug #64529] [ms] confusing diagnostics when starting document with blank line or `KF` call

Follow-up Comment #3, bug#64529 (group groff): [Savannah thinks I'm the submitter, but it's really Doug--unfortunately, this field isn't editable.] ___ Reply to this item at: _

[bug #64529] [ms] confusing diagnostics when starting document with blank line or `KF` call

Follow-up Comment #4, bug#64529 (group groff): [comment #3 comment #3:] > [Savannah thinks I'm the submitter, but it's really Doug--unfortunately, this field isn't editable.] Ah, thanks, Dave. Doug, Any thoughts on comment #1? Regards, Branden ___

[bug #64285] [troff] \D't' (set line thickness) drawing command alters drawing position

Follow-up Comment #11, bug#64285 (group groff): [comment #10 comment #10:] > I _do_ observe some tiny differences (in kerning), for instance: Kerning appears to be done by troff, not the postprocessor: $ diff <(printf 'AVATAR\n' | groff -Z) <(printf '.kern 0\nAVATAR\n' | groff -Z) 12,20c12 < tA <