Follow-up Comment #1, bug #63002 (project groff):
[comment #0 original submission:]
> This example in the Texinfo manual doesn't produce the claimed output.
>
> @Example
> A caf
> \o
> e\'
>
>
> in Paris
> @result{} A café in Paris
> @endExample
>
> First, there are three newline characters (one ending the line, and two more
forming blank lines) following the overstruck "e\'" sequence; the first of
these closes the \o escape,
...and funnily enough, as it happens, is _also_ treated as the end of an input
line.
> as the example is intended to illustrate, but the other two cause a break,
which puts the result not all on one line as shown.
Yup.
> Second, the newline between "caf" and "\o" outputs (in fill mode) a space,
resulting not in "café" but in "caf é".
Yup.
When I last looked at this, a couple of years ago, I got deeply confused and
gave up.
> Example input that produces the claimed output would be:
>
> @Example
> A caf\o
> e\'
> in Paris
>
> This is also visually tighter while still illustrating the ability of
newlines to delimit \o's argument.
Yes.
I independently discovered this while chasing down Bjarni's bug #63011, and
also discovered some worse lies in this part of the manual regarding which
escape sequences do and don't accept newlines as delimiters. So now I have a
big diff fixing this report, those other problems, and syncing the relevant
syntactical info to groff(7) as well. The latter had been punting the reader
to our Texinfo manual--bad form.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63002>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
