unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Mats Lidell <matsl@gnu.org>
Cc: 74042@debbugs.gnu.org
Subject: bug#74042: [PATCH] Accept texi2any for version identification
Date: Sun, 27 Oct 2024 14:01:03 -0700	[thread overview]
Message-ID: <CADwFkmn=8-v+8NzPiy9smD1gK9pOp1xi9gP6YGnry+Knfkdy7w@mail.gmail.com> (raw)
In-Reply-To: <868qu98ide.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> 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?

Because that what the Texinfo documentation tells you to do now.

The Info node (info "(texinfo) Info Files") says:

       Info files are nearly always created by processing a Texinfo
    source document.  ‘texi2any’, also known as ‘makeinfo’, is the
    principal command that converts a Texinfo file into an Info file;
    see texi2any.

    [...]

       With the release of ‘texi2any’ as the reference implementation,
    development of both the C implementation of ‘makeinfo’ and
    ‘texi2html’ has been halted.  Going forward, we ask authors of
    Texinfo documents to use only ‘texi2any’.

Furthermore, the index entry for `makeinfo` in the Texinfo manual leads
to (info "(texinfo) Invoking texi2any"), and there they again tell you
to use `texi2any`:

    To process a Texinfo file, invoke ‘texi2any’ followed by the name of
    the Texinfo file.  Also select the format you want to output with
    the appropriate command line option (default is Info).  Thus, to
    create the Info file for Bison, type the following to the shell:

         texi2any --info bison.texi

> FTR, I'm very unhappy about this change.  I don't think we should
> support this.  It is not future-proof.

I installed it before seeing your objections; I assumed it was
uncontroversial.  I'm probably missing some nuances here as I'm far
removed from Texinfo development, but the documentation at least is
clear.  At the very least, we should support the recommended use of
Texinfo, and that's all that Mats's patch does, AFAICT.





  reply	other threads:[~2024-10-27 21:01 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
2024-10-27 21:01       ` Stefan Kangas [this message]
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='CADwFkmn=8-v+8NzPiy9smD1gK9pOp1xi9gP6YGnry+Knfkdy7w@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=74042@debbugs.gnu.org \
    --cc=eliz@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).