> Date: Sat, 5 Oct 2024 16:02:08 -0700
> From: Per Bothner
>
> On 10/5/24 10:37 AM, Gavin Smith wrote:
> > And that is precisely what I DON'T want to happen. I am not willing to
> > work on texi2any any more if parts of it start being written in C++.
>
> That is sad to hear. It is quite clear t
On 10/5/24 10:37 AM, Gavin Smith wrote:
And that is precisely what I DON'T want to happen. I am not willing to
work on texi2any any more if parts of it start being written in C++.
That is sad to hear. It is quite clear to me that C++ is a much more suited
implementation language than C, at lea
Looking more closely at the gawk.html file for gawk5 5.3.1, from
September 22, I don't see these blank lines. It may be that
you have an old version?
In any case, I have fixed the doc and pushed it to git.
Arnold
arn...@skeeve.com wrote:
> Hi.
>
> Apologies for the delay in replying, I've been
On Sat, Oct 05, 2024 at 11:22:06AM -0600, arn...@skeeve.com wrote:
> IMHO this is really a makeinfo bug (and indeed, the Info file doesn't
> change after this update), so I'm cc-ing the texinfo folks.
I am not sure what the bug is supposed to be here. The bug report
said "ul" and "ol" which I ass
On Sat, Oct 05, 2024 at 08:29:49AM -0700, Per Bothner wrote:
> On 10/5/24 3:00 AM, Gavin Smith wrote:
>
> > This adds C++ code to the project!! This is very concerning. We
> > already have a lot of languages in the Texinfo project: TeX, Perl, C,
> > even JavaScript. I have no desire to understa
On Sat, Oct 05, 2024 at 02:52:55PM +0200, Patrice Dumas wrote:
> > Commit a45bddf685edd (dated 2024-10-05, committed 2024-10-05)
> > "Add C++ code to have an hashmap when Perl is not used"
> >
> > This adds C++ code to the project!! This is very concerning. We
> > already have a lot of languages
Hi.
Apologies for the delay in replying, I've been offline for several
days.
Thank you for the report. I have fixed all the cases in the manual
and will push it to Git shortly. The HTML manual will be updated
when I next make a release.
IMHO this is really a makeinfo bug (and indeed, the Info f
On Sat, Oct 05, 2024 at 02:52:55PM +0200, Patrice Dumas wrote:
> On Sat, Oct 05, 2024 at 11:00:05AM +0100, Gavin Smith wrote:
> > I'd also like to know how many more of these commits are coming.
>
> I still have some conflict/rebasing/cherry picking anomalies that may
> require one or two small co
On Sat, Oct 05, 2024 at 02:38:14PM +0100, Gavin Smith wrote:
> On Sat, Oct 05, 2024 at 01:57:49PM +0100, Gavin Smith wrote:
> > Here's a change to adjust-translations.pl to do this:
>
> ...
>
> > I will commit this once I have updated the test results.
>
> I've commited a change for this script,
On 10/5/24 3:00 AM, Gavin Smith wrote:
This adds C++ code to the project!! This is very concerning. We
already have a lot of languages in the Texinfo project: TeX, Perl, C,
even JavaScript. I have no desire to understand or maintain C++ code
in Texinfo as well. It is also a lot for any new c
On Sat, Oct 05, 2024 at 11:00:05AM +0100, Gavin Smith wrote:
> I'd also like to know how many more of these commits are coming.
Another thing remaining on my TODO list would be an implementation of
XDG base directory for pure C. Not important at all as it would only be
used in the demonstrator pr
On Sat, Oct 05, 2024 at 01:57:49PM +0100, Gavin Smith wrote:
> Here's a change to adjust-translations.pl to do this:
...
> I will commit this once I have updated the test results.
I've commited a change for this script, run it on the translations and
updated the test results.
"maintain/all_test
On Sat, Oct 05, 2024 at 01:02:03PM +0200, Patrice Dumas wrote:
> On Sat, Oct 05, 2024 at 11:28:53AM +0100, Gavin Smith wrote:
> > I see that this was fixed in commit b0eb920e16320727196c (2024-10-03);
> > however the effect of this is that all the translated versions of these
> > strings will now b
On Sat, Oct 05, 2024 at 11:00:05AM +0100, Gavin Smith wrote:
> I'd also like to know how many more of these commits are coming.
I still have some conflict/rebasing/cherry picking anomalies that may
require one or two small commits.
After that, there are 4 commits that are still pending, correspon
On Sat, Oct 05, 2024 at 11:28:53AM +0100, Gavin Smith wrote:
> I see that this was fixed in commit b0eb920e16320727196c (2024-10-03);
> however the effect of this is that all the translated versions of these
> strings will now be wrong:
>
> - - Variable d\'instance de fr : BBB CCC
> + -- Variable
On Sat, Oct 05, 2024 at 11:12:58AM +0100, Gavin Smith wrote:
> libintl-perl was recently upgraded in the Texinfo sources under
> tp/maintain/lib, to version 1.33, but the README file still says:
>
> We ship this version of libintl-perl to be sure that it is available, and
> also to have a cons
On Thu, Oct 03, 2024 at 07:23:26PM +0100, Gavin Smith wrote:
> On Thu, Oct 03, 2024 at 07:06:47PM +0200, Patrice Dumas wrote:
> > It is indeed not necessary and could very well be reverted, either by
> > using --- that will become --, or setting code style for the leading --.
> > I hesitated a lot
On Thu, Oct 03, 2024 at 10:49:44PM +0200, Andreas Schwab wrote:
> On Okt 03 2024, Patrice Dumas wrote:
>
> > On Thu, Oct 03, 2024 at 09:03:16PM +0100, Gavin Smith wrote:
> >> Currently, when I run "make" there are a slew of error messages (see
> >> below).
> >
> > I can't reproduce, maybe because
libintl-perl was recently upgraded in the Texinfo sources under
tp/maintain/lib, to version 1.33, but the README file still says:
We ship this version of libintl-perl to be sure that it is available, and
also to have a consistent behaviour (different gettext implementations do
things differe
On Sun, Sep 29, 2024 at 04:30:40PM +0200, Patrice Dumas wrote:
> On Sun, Sep 29, 2024 at 05:18:58PM +0300, Eli Zaretskii wrote:
> > Why do I suddenly receive from texinfo-comm...@gnu.org a very long
> > series of commits from June and July? I've received about 400 mails
> > like that already since
20 matches
Mail list logo
