Re: Deprecate Texinfo commands

2020-11-17 Thread Gavin Smith
On Tue, Nov 17, 2020 at 08:13:29AM +0100, Werner LEMBERG wrote: > Irrespective of that I wonder what must be done in the future to make > `@smallexample` be output with smaller type in HTML... It's probably not possible. You could make both @example and @smallexample smaller everywhere using CSS.

Re: Deprecate Texinfo commands

2020-11-16 Thread Werner LEMBERG
>> 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 fo

Re: Deprecate Texinfo commands

2020-11-16 Thread Patrice Dumas
On Mon, Nov 16, 2020 at 09:34:38PM +, Gavin Smith wrote: > > 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 he

Re: Deprecate Texinfo commands

2020-11-16 Thread Gavin Smith
On Mon, Nov 16, 2020 at 09:26:43PM +0100, Patrice Dumas wrote: > On Mon, Nov 16, 2020 at 07:10:12PM +, 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 wo

Re: Deprecate Texinfo commands

2020-11-16 Thread Patrice Dumas
On Mon, Nov 16, 2020 at 07:10:12PM +, 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 co

Re: Deprecate Texinfo commands

2020-11-16 Thread Gavin Smith
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 sep

Re: Deprecate Texinfo commands

2020-11-12 Thread Patrice Dumas
On Thu, Nov 12, 2020 at 07:07:24AM +, Gavin Smith wrote: > On Thu, Nov 12, 2020 at 01:13:12AM +0100, Patrice Dumas wrote: > > On Wed, Nov 11, 2020 at 07:05:17PM +, Gavin Smith wrote: > > > > > > > > I think that the arguments should be separated by commas both for > > > > consistency and a

Re: Deprecate Texinfo commands

2020-11-12 Thread Werner LEMBERG
>> > 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

Re: Deprecate Texinfo commands

2020-11-11 Thread Gavin Smith
On Thu, Nov 12, 2020 at 01:13:12AM +0100, Patrice Dumas wrote: > On Wed, Nov 11, 2020 at 07:05:17PM +, Gavin Smith wrote: > > > > > > 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.

Re: Deprecate Texinfo commands

2020-11-11 Thread Patrice Dumas
On Wed, Nov 11, 2020 at 07:05:17PM +, Gavin Smith wrote: > > > > 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 sema

Re: Deprecate Texinfo commands

2020-11-11 Thread Gavin Smith
On Wed, Nov 11, 2020 at 07:43:56PM +0100, Patrice Dumas wrote: > On Tue, Nov 10, 2020 at 08:30:15PM +, 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

Re: Deprecate Texinfo commands

2020-11-11 Thread Patrice Dumas
On Tue, Nov 10, 2020 at 08:30:15PM +, 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

Re: Deprecate Texinfo commands

2020-11-10 Thread Gavin Smith
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 p

Re: Deprecate Texinfo commands

2020-11-08 Thread Werner LEMBERG
>> So what is the right way to make an environment display at a >> smaller size in HTML output? Sometimes examples have really long >> lines, making horizontal screen scrolling uncomfortable... > > I don't have an answer to this. Ouch :-) > It seems to me that the problem of too long lines is d

Re: Deprecate Texinfo commands

2020-11-08 Thread Gavin Smith
On Sun, Nov 08, 2020 at 06:07:20AM +0100, Werner LEMBERG wrote: > > > @smallexample and friends. Simpler to use @example instead. If > > people desperately want to use smaller fonts in the printed output > > they could use > > > > @set dispenvsize small > > > > instead, which is only used by

Re: Deprecate Texinfo commands

2020-11-07 Thread Werner LEMBERG
> @smallexample and friends. Simpler to use @example instead. If > people desperately want to use smaller fonts in the printed output > they could use > > @set dispenvsize small > > instead, which is only used by texinfo.tex and doesn't affect > anything else. So what is the right way to m

Deprecate Texinfo commands

2020-11-07 Thread Gavin Smith
I'd like to suggest that some Texinfo commands could be marked as deprecated, with warnings could be introduced to encourage people to remove these commands from their documents/config files. Some rarely used commands could possibly even be removed at some point in the future. @definfoenclose. I