Follow-up Comment #20, bug #67207 (group groff): [comment #18 comment #18:] > the .SY line has interpreted "\\-" as "\-" but the following > line it has stayed as "\\-". Must be a bug in echo
My "echo" appears to be interpreting all backslashes the same; it is groff
that differentiates them. I simplified the test case, and had it show raw
output from "echo" and then that same output piped into groff.
$ cat echo-test
#!/bin/sh
input3='.
.TH foo 1
.P
.SY \\%command\\-name
\\%\\-\\-interminable\\-option
.'
echo "$input3"
echo "$input3" | groff -rLL=80n -man -T ascii -P -cbou
$ ./echo-test
.
.TH foo 1
.P
.SY \\%command\\-name
\\%\\-\\-interminable\\-option
.
foo(1) General Commands Manual
foo(1)
command-name \%\-\-interminable\-option
foo(1)
This makes sense to me; groff _ought_ to parse backslashes differently in
macro arguments than in top-level input. But it doesn't explain why Deri and
I see different results than Branden does.
The above output is effectively the same--having only whitespace
differences--whether I use groff 1.22.4, 1.23, or git HEAD.
(This side quest is threatening to overrun this ticket's actual purpose, which
suggests opening a new one, but substantial history for both issues is already
here, so they're hard to disentangle now.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67207>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
