On Tue, Jan 12, 2021 at 08:10:46PM +0000, Gavin Smith wrote: > On Mon, Jan 04, 2021 at 10:46:20PM +0100, Patrice Dumas wrote: > > On Sat, Jan 02, 2021 at 12:36:28PM +0000, Gavin Smith wrote: > > > The main area of work that I can see before the next Texinfo release is > > > made is compatibility of the XS parser with the Perl parser. > > > > > > I have started some work on testing manuals and automatically looking > > > for differences in the output, but need to do more on this. Basically, > > > I have a short shell script with a loop in it like this: > > > > > > for m in $manuals; do > > > x=X/`basename $m`.info > > > p=P/`basename $m`.info > > > TEXINFO_XS=require texi2any $m -o $x --no-split > > > TEXINFO_XS=omit texi2any $m -o $p --no-split > > > diff $x $p > > > done > > > > > > I also need to document that @example can take an argument. > > > > Is the design of that decided? I would still be in favor of > > * having arguments separated by comma , > > * giving a meaning to the first argument (the language) and the > > second (small or not for compatibilities with @smallexample and > > others). > > Implemented and documented now.
Thanks. It looks good to me. I think that the expansion part may not give something fully correct if there are @-commands, but it is not a typical nor documented case. I would still prefer that case to be covered in tests, but it is not a priority at all, and in my opinion do not need to delay a release. -- Pat
