On Tue, 2023-09-05 at 10:27 +0200, Patrice Dumas wrote:
> On Mon, Sep 04, 2023 at 10:00:42PM +0200, Jonas Hahnfeld wrote:
> > As I write above, label_target_name is already called for external
> > references (via _normalized_label_id_file). So all we would need is
> > something like node_file_name
On Mon, Sep 04, 2023 at 10:00:42PM +0200, Jonas Hahnfeld wrote:
> As I write above, label_target_name is already called for external
> references (via _normalized_label_id_file). So all we would need is
> something like node_file_name for external nodes (or just use the same
> function) and a hook
On Mon, Sep 04, 2023 at 10:00:42PM +0200, Jonas Hahnfeld wrote:
> On Mon, 2023-09-04 at 13:29 +0200, Patrice Dumas wrote:
> > On Tue, Aug 29, 2023 at 10:58:21AM +0200, Jonas Hahnfeld wrote:
>
> > The other reason is that there is a translation to C of perl code
> > going on with, hopefully, the po
On Mon, Sep 04, 2023 at 10:00:42PM +0200, Jonas Hahnfeld via Bug reports for
the GNU Texinfo documentation system wrote:
> Does this mean texi2any will move away from being a pure Perl program?
It already has although pure Perl code exists as a backup in case the
C parts couldn't be built or load
On Mon, 2023-09-04 at 13:29 +0200, Patrice Dumas wrote:
> On Tue, Aug 29, 2023 at 10:58:21AM +0200, Jonas Hahnfeld wrote:
>
> > A couple of specific questions to start with:
> > * For lilypond_label_target_name, we need to deal with three different
> > function signatures if we want to support a
On Tue, Aug 29, 2023 at 10:58:21AM +0200, Jonas Hahnfeld via Bug reports for
the GNU Texinfo documentation system wrote:
> Dear Texinfo / texi2any developers,
>
> if some of the experts have time, I would highly appreciate some
> feedback on a texi2any customization file for LilyPond:
> https://g
On Sun, Sep 03, 2023 at 12:57:10AM +0100, Gavin Smith wrote:
> On Sat, Sep 02, 2023 at 09:03:12AM +0100, Gavin Smith wrote:
> > On Sat, Sep 02, 2023 at 12:22:52AM +0100, Gavin Smith wrote:
> > > Here's the change I'm looking at currently:
> >
> > The change with futher work is below.
>
> I commit
On Sat, Sep 02, 2023 at 09:03:12AM +0100, Gavin Smith wrote:
> On Sat, Sep 02, 2023 at 12:22:52AM +0100, Gavin Smith wrote:
> > Here's the change I'm looking at currently:
>
> The change with futher work is below.
I committed something like this but left warnings alone.
> It may be difficult to
On Sat, Sep 02, 2023 at 12:22:52AM +0100, Gavin Smith wrote:
> Here's the change I'm looking at currently:
The change with futher work is below.
It may be difficult to get the encoding status of the text right:
$ cat warn2.init
warn "Datei konnte nicht geöffnet werden";
$ ../tp/texi2any.pl --i
On Wed, Aug 30, 2023 at 10:48:19AM +0200, Jonas Hahnfeld wrote:
> On Wed, 2023-08-30 at 00:08 +0100, Gavin Smith wrote:
> > On Tue, Aug 29, 2023 at 10:58:21AM +0200, Jonas Hahnfeld wrote:
> > > Is it possible to make texi2any fail if there is a syntax error or
> > > other severe problems in an init
On Wed, 2023-08-30 at 17:07 +0100, Gavin Smith wrote:
> Okay, in this case there doesn't seem to be any point in continuing the
> program (and the exit status should be non-zero). We'll have to see if
> these errors can be distinguished from mere warnings.
>
> I can imagine the current behaviour
On Wed, Aug 30, 2023 at 10:48:19AM +0200, Jonas Hahnfeld wrote:
> Not quite, I'm fine with warnings not resulting in errors (even though
> a -Werror like flag would be a nice addition!)
>
> > However, I don't fully understand what the problem is with carrying on.
> > Could you not test the code wi
On Wed, 2023-08-30 at 00:08 +0100, Gavin Smith wrote:
> On Tue, Aug 29, 2023 at 10:58:21AM +0200, Jonas Hahnfeld wrote:
> > Is it possible to make texi2any fail if there is a syntax error or
> > other severe problems in an initialization file? Right now, the 'eval'
> > call only seems to emit a war
On Tue, Aug 29, 2023 at 10:58:21AM +0200, Jonas Hahnfeld via Bug reports for
the GNU Texinfo documentation system wrote:
> Dear Texinfo / texi2any developers,
>
> if some of the experts have time, I would highly appreciate some
> feedback on a texi2any customization file for LilyPond:
> https://g
Dear Texinfo / texi2any developers,
if some of the experts have time, I would highly appreciate some
feedback on a texi2any customization file for LilyPond:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2089
As a bit of context, LilyPond uses texi2html for its HTML documentation
since quit
15 matches
Mail list logo
