On 7 October 2015 at 23:59, Quinn Grier <[email protected]> wrote: > Is consistency with @inlineraw also a consideration? It seems to be more > friendly with paragraphs: > > @inlineraw{html, foo} > bar > > produces > > <p>foo > bar > </p> > > and even the @inlineraw by itself gives a <p> element. One might expect > that a raw block is interchangeable with an @inlineraw command with the > block body as its argument and with added whitespace, similar to how the > manual states that @inlinefmt{html, x} "is nearly equivalent to" @ifhtml > "except that no whitespace is added".
I see, there is a newline at the end of an @ifhtml block, but not (at present) for html. Input: \input texinfo @html foo1 gaaz1 @end html bar bas @html foo2 gaaz2 @end html bar @ifhtml FOO1 GAAZ1 @end ifhtml BAR BAS @ifhtml FOO2 GAAZ2 @end ifhtml BAR @bye Output: foo1 gaaz1<p>bar </p> <p>bas foo2 gaaz2bar </p> <p>FOO1 GAAZ1 BAR </p> <p>BAS FOO2 GAAZ2 BAR </p> Notably compare the joined "gaaz2bar" with "GAAZ2" and "BAR" on separate lines. Re this: > One might expect > that a raw block is interchangeable with an @inlineraw command with the > block body as its argument and with added whitespace, an @html block certainly should not open a paragraph, leading a "<p>" tag to be output. I would guess that if someone really needed an @html block inside a paragraph, they could do @indent @html whatever @end html more although I haven't checked - or just use @inlineraw.
