[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Use "simple parsers" for translations again?
From: |
Gavin Smith |
Subject: |
Re: Use "simple parsers" for translations again? |
Date: |
Sat, 25 Nov 2023 17:35:47 +0000 |
On Sat, Nov 25, 2023 at 09:35:28AM +0100, Patrice Dumas wrote:
> > It seems that we could stop these structures being modified with the
> > addition of a flag on the parser (e.g. $parser->{'locked'} or
> > $parser->{'simple'}). Then check this flag any time:
> >
> > * A new Texinfo command is to be defined (@macro, @alias, @definfoenclose).
> > * A new index is to be added (@defindex, @defcodeindex).
> >
> > Then the change to the state wouldn't be made if the flag was set, and
> > possibly a warning message could be given too.
> >
> > I can try to work on a patch for this if this approach sounds like a
> > good idea.
>
I've sent a series of three patches to bug-texinfo@gnu.org.
- Re: Post release texi2any performance regression, Gavin Smith, 2023/11/04
- Re: Post release texi2any performance regression, Patrice Dumas, 2023/11/04
- Re: Post release texi2any performance regression, Gavin Smith, 2023/11/04
- Re: Post release texi2any performance regression, Gavin Smith, 2023/11/04
- Re: Post release texi2any performance regression, Patrice Dumas, 2023/11/05
- Use "simple parsers" for translations again?, Gavin Smith, 2023/11/24
- Re: Use "simple parsers" for translations again?, Patrice Dumas, 2023/11/25
- Re: Use "simple parsers" for translations again?, Gavin Smith, 2023/11/25
- Re: Use "simple parsers" for translations again?,
Gavin Smith <=
- Re: Post release texi2any performance regression, Gavin Smith, 2023/11/04
- Re: Post release texi2any performance regression, Patrice Dumas, 2023/11/05
- Re: Post release texi2any performance regression, Gavin Smith, 2023/11/05
- Re: Post release texi2any performance regression, Patrice Dumas, 2023/11/05
- Re: Post release texi2any performance regression, Gavin Smith, 2023/11/05