Re: Deprecate Texinfo commands

[Gavin Smith]

On Mon, Nov 16, 2020 at 09:26:43PM +0100, Patrice Dumas wrote:
> On Mon, Nov 16, 2020 at 07:10:12PM +0000, Gavin Smith wrote:
> > On Thu, Nov 12, 2020 at 02:33:52PM +0100, Werner LEMBERG wrote:
> > > 
> > > >> > One idea is to change Texinfo to allow @example to have an
> > > >> > argument which would be output as a 'class' in HTML.  [...]
> > > > 
> > > > Implemented in commit 758870e30b.  You can give more than one
> > > > argument to @example separated by spaces, and they will be appended
> > > > to the class attribute on the <div>.
> > > 
> > > Thanks.  Am I correct that a TeX implementation is still missing?
> > 
> > I've made it so that any argument to @example will be ignored.  So this
> > argument can be given and it will be OK to process with TeX, but this
> > argument couldn't be used to customize or post-process the example block
> > for TeX output.
> 
> What about using commas between the arguments?

I don't feel strongly about it as it's not clear exactly what multiple
arguments might be used for.  It would certainly be more consistent with
other Texinfo commands if arguments were separated with commas.  This would
also help with normalizing whitespace, e.g.

@example lisp , small     ,blackletter,executable
...
@end example

would be output with class='example lisp small blackletter executable'.
I don't think the order of the arguments should matter.  It would
also help with checking validity of class names, for duplicates,
and possibly for particular class names that should be avoided.