Re: texi2any's equivalent for texi2html's option `--short-ref`

2022-01-06 Thread Werner LEMBERG
Hello Gavin and Patrice, >> `texi2html` had an option `--short-ref` [...] > > I had a look at the history and this customization never made to > texi2any, however, previously if the reference was to a section, > there was 'section'. This was removed in that commit > > https://git.savannah.gnu.

Re: texi2any's equivalent for texi2html's option `--short-ref`

2022-01-06 Thread Patrice Dumas
On Thu, Jan 06, 2022 at 04:56:34PM +, Werner LEMBERG wrote: > > `texi2html` had an option `--short-ref` that removed the word > 'section' in link texts (version 1.82 had also the unfortunate side > effect of removing tags like `...` from the link texts, > but this is another story). > > Looki

Re: texi2any's equivalent for texi2html's option `--short-ref`

2022-01-06 Thread Gavin Smith
On Thu, Jan 06, 2022 at 04:56:34PM +, Werner LEMBERG wrote: > > `texi2html` had an option `--short-ref` that removed the word > 'section' in link texts (version 1.82 had also the unfortunate side > effect of removing tags like `...` from the link texts, > but this is another story). > > Looki

Re: question about a class for list without mark @itemize @w

2022-01-06 Thread Gavin Smith
On Thu, Jan 06, 2022 at 11:31:45AM +0100, Patrice Dumas wrote: > On Wed, Jan 05, 2022 at 09:20:28PM +, Gavin Smith wrote: > > > > I think mark-none would be fine. > > Ok. > > > I saw no-bullet was being used in the current output; that would be okay > > too. (See below.) > > I would prefer

texi2any's equivalent for texi2html's option `--short-ref`

2022-01-06 Thread Werner LEMBERG
`texi2html` had an option `--short-ref` that removed the word 'section' in link texts (version 1.82 had also the unfortunate side effect of removing tags like `...` from the link texts, but this is another story). Looking up the current git's info pages for texinfo I couldn't find an equivalent

Re: `@pxref`: contradicting statements in manual

2022-01-06 Thread Jean-Christophe Helary
> On Jan 6, 2022, at 20:56, Eli Zaretskii wrote: > >> From: Jean-Christophe Helary >> Date: Thu, 6 Jan 2022 18:31:44 +0900 >> Cc: Werner LEMBERG , >> bug-texinfo@gnu.org >> I'd love to have a recommendation not to use tags that add arbitrary English strings :-) Unless there i

Re: `@pxref`: contradicting statements in manual

2022-01-06 Thread Eli Zaretskii
> From: Jean-Christophe Helary > Date: Thu, 6 Jan 2022 18:31:44 +0900 > Cc: Werner LEMBERG , > bug-texinfo@gnu.org > > >> I'd love to have a recommendation not to use tags that add arbitrary > >> English strings :-) > >> Unless there is a working (easy to use and well documented) mechanism to

Re: question about a class for list without mark @itemize @w

2022-01-06 Thread Patrice Dumas
On Wed, Jan 05, 2022 at 09:20:28PM +, Gavin Smith wrote: > > I think mark-none would be fine. Ok. > I saw no-bullet was being used in the current output; that would be okay > too. (See below.) I would prefer to replace it with more semantic classes, but we will see. > But it doesn't matte

Re: `@pxref`: contradicting statements in manual

2022-01-06 Thread Jean-Christophe Helary
> On Jan 6, 2022, at 18:12, Eli Zaretskii wrote: > >> From: Jean-Christophe Helary >> Date: Thu, 6 Jan 2022 17:27:18 +0900 >> Cc: bug-texinfo@gnu.org >> >> I'd love to have a recommendation not to use tags that add arbitrary English >> strings :-) >> Unless there is a working (easy to use a

Re: `@pxref`: contradicting statements in manual

2022-01-06 Thread Eli Zaretskii
> From: Jean-Christophe Helary > Date: Thu, 6 Jan 2022 17:27:18 +0900 > Cc: bug-texinfo@gnu.org > > I'd love to have a recommendation not to use tags that add arbitrary English > strings :-) > Unless there is a working (easy to use and well documented) mechanism to > localize said strings. ???

Re: `@pxref`: contradicting statements in manual

2022-01-06 Thread Eli Zaretskii
> Date: Thu, 06 Jan 2022 08:17:45 + (UTC) > From: Werner LEMBERG > > The `@ref` command can tempt writers to express themselves in a > manner that is suitable for a printed manual but looks awkward in > the Info format. Bear in mind that your audience could be using > both the printe

Re: `@pxref`: contradicting statements in manual

2022-01-06 Thread Jean-Christophe Helary
> On Jan 6, 2022, at 17:17, Werner LEMBERG wrote: > > > > The documentation > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040pxref.html > says: > > The effect of `@pxref{node-name}` is similar to that of `see > @ref{node-name}`. However, in many circumstance the latte

`@pxref`: contradicting statements in manual

2022-01-06 Thread Werner LEMBERG
The documentation https://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040pxref.html says: The effect of `@pxref{node-name}` is similar to that of `see @ref{node-name}`. However, in many circumstance the latter is preferrable, as this makes it clear in the Info output that the