[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deprecate Texinfo commands

From: Patrice Dumas
Subject: Re: Deprecate Texinfo commands
Date: Wed, 11 Nov 2020 19:43:56 +0100

On Tue, Nov 10, 2020 at 08:30:15PM +0000, Gavin Smith wrote:
> On Sun, Nov 08, 2020 at 10:39:02AM +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.  [...]
> > 
> > Basically, your suggestions are sound – they kind-of resemble the
> > markdown extensions introduced by pandoc...
> 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>.

I think that the arguments should be separated by commas both for
consistency and also because we eventually want to allow for spaces in
arguments.  Also I think that it would be much better if the arguments
were semantically defined.  The first argument could be the language,
the second a hint about the size.

> Now @lisp is equivalent to "@example lisp".
> Documentation is still to be done.
> > I could imagine the following, which is quite simple:
> > 
> >   @example       →  <pre class="example">
> >   @smallexample  →  <pre class="smallexample">
> > 
> > etc., etc., with a corresponding setup in texi2any's default CSS code.
> The problem is that all of the default CSS rules are always output, and
> this leads to a CSS block that is quite long, which gets in the way when
> you are looking at the HTML file, for the sake of something that is
> fairly rare.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]