At 2025-02-22T16:38:00+0100, onf wrote: > I forgot to emphasize the likely largest obstacle, which is the fact > that it
(presumably Savannah #66625, and/or changes already in Git) > would break compatibility with documents written for neatroff. In what way? > Ali seems averse to breaking backwards compatibility with both AT&T > troff and past versions of neatroff. That's a reasonable inclination. I think a more accurate characterization of the changes I have made and am proposing, however, is that things that simply never could work before, now can. > I feel like changing ab, hpf, hpfa, nx, so, and tm (the others aren't > implemented by neatroff) to allow spaces in the middle of their > arguments might have more chance of success. I begin to get the feeling you're not paying close attention to what I'm saying in emails, what I've quoted from the "NEWS" file,[1] or how GNU troff actually behaves. Here are exhibits of GNU troff behavior from 1.22.3 and Git HEAD when encountering spaces in the middle of arguments to the requests you name. $ printf '.ab this is groff \\n[.x].\\n[.y].\\n[.Y]\n' | ~/groff-1.22.3/bin/groff this is groff 1.22.3 $ printf '.ab this is groff \\n[.x].\\n[.y].\\n[.Y]\n' | ~/groff-HEAD/bin/groff this is groff 1.23.0 $ cp ~/groff-HEAD/share/groff/1.23.0/tmac/hyphen.en "/tmp/english hyphenation patterns" $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.hpf /tmp/english hyphenation patterns\n' | ~/groff-1.22.3/bin/groff this is groff 1.22.3 <standard input>:2: can't find hyphenation patterns file `/tmp/english' $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.hpf /tmp/english hyphenation patterns\n' | ~/groff-HEAD/bin/groff this is groff 1.23.0 $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.hpfa /tmp/english hyphenation patterns\n' | ~/groff-1.22.3/bin/groff this is groff 1.22.3 <standard input>:2: can't find hyphenation patterns file `/tmp/english' $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.hpfa /tmp/english hyphenation patterns\n' | ~/groff-HEAD/bin/groff this is groff 1.23.0 $ echo 'This is the story of my life.' > '/tmp/My Life.groff' $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.nx /tmp/My Life.groff\n' | ~/groff-1.22.3/bin/groff -a this is groff 1.22.3 <standard input>:2: can't open `/tmp/My': No such file or directory $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.nx /tmp/My Life.groff\n' | ~/groff-HEAD/bin/groff -a this is groff 1.23.0 <beginning of page> This is the story of my life. $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.so /tmp/My Life.groff\n' | ~/groff-1.22.3/bin/groff -a this is groff 1.22.3 <standard input>:2: can't open `/tmp/My': No such file or directory $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n.so /tmp/My Life.groff\n' | ~/groff-HEAD/bin/groff -a this is groff 1.23.0 <beginning of page> This is the story of my life. $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n' | ~/groff-1.22.3/bin/groff this is groff 1.22.3 $ printf '.tm this is groff \\n[.x].\\n[.y].\\n[.Y]\n' | ~/groff-HEAD/bin/groff this is groff 1.23.0 How does any of the above illustrate a break of compatibility with AT&T troff, or with neatroff? I encourage you to examine the behavior of AT&T troff with respect to the `ab`, `nx`, `so`, and `tm` requests. I have pointed you several times to the comments in Savannah #65108,[2] to apparently little avail. Regards, Branden [1] https://git.savannah.gnu.org/cgit/groff.git/tree/NEWS [2] https://savannah.gnu.org/bugs/?65108
signature.asc
Description: PGP signature
