[bug #65960] pre-html.cpp: replace "pnmcut" with "pamcut"

Update of bug #65960 (group groff): Item Group:Lint => Feature change Status:None => In Progress Assigned to:None => gbranden __

[bug #65960] [grohtml] pre-html.cpp: replace "pnmcut" with "pamcut"

Update of bug #65960 (group groff): Summary: pre-html.cpp: replace "pnmcut" with "pamcut" => [grohtml] pre-html.cpp: replace "pnmcut" with "pamcut" ___ Reply to this item at:

[bug #65962] [troff] describe use of `slimit` register better

Update of bug #65962 (group groff): Severity:1 - Wish => 3 - Normal Item Group: Build/Installation => Documentation Status: Postponed => In Progress Assigned to:

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

Update of bug #64071 (group groff): Summary: [troff] support construction of proper C strings for request arguments destined for the shell or file system => [troff] support construction of proper C strings for request arguments destined for the shell _

[bug #62787] [troff] support construction of proper C strings for messages sent to the standard error stream

Update of bug #62787 (group groff): Summary: [troff] standard error output should be sanitized => [troff] support construction of proper C strings for messages sent to the standard error stream ___ Follow-up Comment #5: Th

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

Follow-up Comment #1, bug #65108 (group groff): This would affect the `\O` escape sequence and the `cf`, `fp`, `hpf`, `hpfa`, `mso`, `msoquiet`, `nx`, `open`, `opena`, `psbb`, `so`, `soquiet`, and `trf` requests. Right now at least some of these use the internal function `get_long_name()`, which

[bug #64577] [grops] can't embed/download fonts from a subdirectory

Follow-up Comment #16, bug #64577 (group groff): I haven't forgotten about this. It applies pressure to limitations elsewhere in the system; see bug #65108. ___ Reply to this item at: ___

[bug #65961] [grohtml] pre-html.cpp: suppress certain warnings from pnmcrop

Update of bug #65961 (group groff): Summary: pre-html.cpp: suppress spurious warnings from buggy pnmcrop => [grohtml] pre-html.cpp: suppress certain warnings from pnmcrop ___ Follow-up Comment #2: Not sure I agree with you

[bug #65960] [grohtml] pre-html.cpp: replace "pnmcut" with "pamcut"

Update of bug #65960 (group groff): Category: Preprocessor html => Preprocessor - others/general ___ Reply to this item at: ___ Me

[bug #65960] [grohtml] pre-html.cpp: replace "pnmcut" with "pamcut"

Update of bug #65960 (group groff): Category: Preprocessor - others/general => Preprocessor html ___ Follow-up Comment #2: Oops. ___ Reply to this item at:

[bug #65967] [PATCH] [docs] Say "input" instead of "input file" where appropriate

Follow-up Comment #1, bug #65967 (group groff): Mom documentation appears to be clean in this regard. "Input file" refers in all cases to source files. ___ Reply to this item at:

[bug #65961] [grohtml] pre-html.cpp: suppress certain warnings from pnmcrop

Update of bug #65961 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #65961] [grohtml] pre-html.cpp: suppress certain warnings from pnmcrop

Follow-up Comment #3, bug #65961 (group groff): [comment #2 comment #2:] > Not sure I agree with you this time, Dave. I'm not always right! > if it's a bug, then it looks to me like it's a bug in _pre-grohtml_ > for passing empty rectangular regions of the page image to > _pnmcrop_ in the first

[bug #65961] [grohtml] pre-html.cpp: suppress certain warnings from pnmcrop

Follow-up Comment #4, bug #65961 (group groff): [comment #3 comment #3:] > Be that as it may, pnmcrop is _also_ throwing the diagnostic on > images that do have content: processing the latest ms.ms with the > latest grohtml produces the diagnostic 59 times with my version > of netpbm (10.70.0)

[bug #65967] [PATCH] [docs] Say "input" instead of "input file" where appropriate

Update of bug #65967 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #65967] [PATCH] [docs] Say "input" instead of "input file" where appropriate

Follow-up Comment #2, bug #65967 (group groff): @@ -16315,7 +16315,7 @@ @node I/O @cindex read next file (@code{nx}) @cindex file, next, read (@code{nx}) @cindex next file, read (@code{nx}) -Stop processing the input file. If @var{file} is specified, read it; +Stop processing the input. If @

[bug #65886] [PATCH] repeated word in some man pages

Update of bug #65886 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #65967] [PATCH] [docs] Say "input" instead of "input file" where appropriate

Follow-up Comment #3, bug #65967 (group groff): True, this might require a deeper rewording to clarify. But the point I'm trying to make here is that .nx can interrupt any input, not just an input file. $ cat interruption No going back! $ printf "You'll see me.\n.nx interruption\nYou won't see m

[bug #64189] [PATCH] [me] for -me developers, document @ register

Update of bug #64189 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Follow-up Comment #1: Will apply, in whittled

[bug #65967] [PATCH] [docs] Say "input" instead of "input file" where appropriate

Follow-up Comment #4, bug #65967 (group groff): It's perhaps a little clearer the way it's presented (post-patch) in groff(7): *.nx*Stop processing the input file and read the next, if any. *.nx* _file_ Stop processing the input and read _file_. But even here I fudged a bit, becaus

[bug #65099] 1.24.0 release goals

Update of bug #65099 (group groff): Depends on: => bugs #65108 ___ Reply to this item at: ___ Message

[bug #65099] 1.24.0 release goals

Update of bug #65099 (group groff): Depends on: => bugs #62787 ___ Reply to this item at: ___ Message