From: Eli Zaretskii <eliz@gnu.org>
To: Mats Lidell <matsl@gnu.org>
Cc: 74042@debbugs.gnu.org
Subject: bug#74042: [PATCH] Accept texi2any for version identification
Date: Sun, 27 Oct 2024 21:18:21 +0200 [thread overview]
Message-ID: <868qu98ide.fsf@gnu.org> (raw)
In-Reply-To: <87plnl4epo.fsf@gnu.org> (message from Mats Lidell on Sun, 27 Oct 2024 18:50:59 +0100)
> From: Mats Lidell <matsl@gnu.org>
> Cc: 74042@debbugs.gnu.org
> Date: Sun, 27 Oct 2024 18:50:59 +0100
>
> Hi Eli,
>
> > Eli Zaretskii writes:
> > Can you explain the rationale? IOW, when does the current code not
> > doing its job?
>
> If the user generates the info file by using texi2any the check for version
> number fails and the fact that "index cookies" are supported is lost.
Why would users do that by invoking texi2any directly?
> > The fact that makeinfo invokes texi2any is an internal implementation
> > detail of the Texinfo project, and I wouldn't want us to depend on
> > that without a very good reason. E.g., once upon a time, makeinfo was
> > a standalone program written in C, and nothing prevents the Texinfo
> > folks from doing that again in some future release.
>
> It seems to be a legit case to use texi2any directly, even encouraged, due to
> being a generic translator. makeinfo is mentioned as being an alias with no
> different behavior. On my system makeinfo is a symbolic link to texi2any.
>
> https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Generic-Translator-texi2any.html
FTR, I'm very unhappy about this change. I don't think we should
support this. It is not future-proof.
next prev parent reply other threads:[~2024-10-27 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 8:35 bug#74042: [PATCH] Accept texi2any for version identification Mats Lidell
2024-10-27 9:20 ` Eli Zaretskii
2024-10-27 17:50 ` Mats Lidell
2024-10-27 19:18 ` Eli Zaretskii [this message]
2024-10-27 21:01 ` Stefan Kangas
2024-10-27 21:33 ` Mats Lidell
2024-10-28 3:23 ` Eli Zaretskii
2024-10-27 9:47 ` Stefan Kangas
2024-10-27 10:11 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868qu98ide.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74042@debbugs.gnu.org \
--cc=matsl@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).