Re: luatex problems with texinfo.tex

2015-12-30 Thread Werner LEMBERG
> I guess we're talking about U+00A7, the section sign, \S in > plain.tex? Yes, and \P. Note, however, that both @S and @P work within a texinfo document. It's just that texinfo.tex's \DeclareUnicodeCharacter for `§' and `¶' (which use `\S' and `\P' for its definition) seem to be modified, resu

Re: luatex problems with texinfo.tex

2015-12-30 Thread Karl Berry
Processing the attached document with luatex, I get I guess we're talking about U+00A7, the section sign, \S in plain.tex? I suppose something somewhere is overwriting that definition, and we should \let the plain \S as some other longer name to avoid the problem. (Plain LuaTeX itself does n

Re: luatex problems with texinfo.tex

2015-12-30 Thread Werner LEMBERG
> §, ¶ Sigh. This should be §, ¶ of course. Werner

luatex problems with texinfo.tex

2015-12-30 Thread Werner LEMBERG
> Processing the attached document [...] Oops! Apparently the wrong file encoding, so here's another try. \input texinfo.tex @documentencoding UTF-8 §, ¶ @bye

luatex problems with texinfo.tex

2015-12-30 Thread Werner LEMBERG
Processing the attached document with luatex, I get ! Undefined control sequence. l.7 which assigns the symbols *, †, ‡, § , ¶ to It works just fine with pdtex. A bug? Werner \input texinfo.tex @documentencoding UTF-8 §, ¶ @bye

Re: texinfo-6.0.91 pretest

2015-12-30 Thread Gavin Smith
On 30 December 2015 at 07:00, Norbert Preining wrote: > Thanks, the old tests now all suceed here, but a new one fails: > FAIL: test_scripts/coverage_formatting_utf8_enable_encoding.sh Thanks, you must have run the long checks. I know why this is failing: it's due to a difference between the resu