>> Mhmm, more tests show that for `@code{foo--bar}` there is no
>> `@discretionary` after the two hyphens. Is this intentional?
>
> Yes, it is. This was to stop hyphenation in @option{--option}.
OK. I guess it isn't easily possible to make TeX insert a
discretionary after two hyphens in the
On Fri, Jan 13, 2023 at 11:10:31PM +0100, Patrice Dumas wrote:
> If I recall well, the idea was that even an empty @w{} would lead to
> some output such that if within a string, the string would not end eup
> contiguous in XML based outputs. For example to avoid $Id$ keywords
> expansion that are
On Wed, Jan 04, 2023 at 01:59:26PM +0100, Patrice Dumas wrote:
> On Mon, Jan 02, 2023 at 09:39:33AM -0800, Raymond Toy wrote:
> > On Sun, Jan 1, 2023 at 10:12 AM Patrice Dumas wrote:
> >
> > > I do not remember any discussion about that. But it is not clear to me
> > > what should be done. Ther
On Fri, Jan 13, 2023 at 09:01:41PM +, Gavin Smith wrote:
> I've checked the important output formats (texinfo.tex, HTML, Info, DocBook,
> LaTeX) and it seems that there isn't much more to be done on either @w or
> @verb to get consistency across the output formats.
>
> The main thing I found w
On Thu, Jan 12, 2023 at 07:34:23AM +, Werner LEMBERG wrote:
>
> >> However, I've tried to fix it in commit bdb7f23072 (texinfo.tex
> >> version 2023-01-11.18).
> >
> > It works, thanks!
>
> Mhmm, more tests show that for `@code{foo--bar}` there is no
> `@discretionary` after the two hyphens.
On Sat, Jan 07, 2023 at 09:34:29PM +, Gavin Smith wrote:
> On Sat, Dec 10, 2022 at 03:11:48PM +, Gavin Smith wrote:
> > On Sat, Dec 10, 2022 at 11:34:47AM +, Gavin Smith wrote:
> > > The commands were clearly based on the corresponding LaTeX commands,
> > > which we should take as autho
