From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) by sourceware.org (Postfix) with ESMTPS id BAE113891037 for ; Mon, 12 Jul 2021 17:15:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BAE113891037 Received: by mail-wr1-x429.google.com with SMTP id k4so20334019wrc.8 for ; Mon, 12 Jul 2021 10:15:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=/yjajTc3v/9Xl9+UJcMkFY7gbWxE0vLxQ7g+N+KmV/A=; b=UKFEHucznnoFdkDoF7g6BOl0POpubVCh0TZ6qtEHbw0q5gjSfeNRt5sMxk7r4KfTBa X2oK+ROIlIo33b6OkpOoqmniNvzV3nNGRmuIqtc3RcUPO0Z2leu+S3zsNEuC3K2nDnuL fiRS6KlQkgt4CyEy+jDr4GUBP8O5P5YuMpVSPgjuBVd8A+FYfttsGOEOZ0h7S9wDsU+o RAfwX5ngiyD85DeBkc3XgbZ97VJ4KXqDw0RFGfKBTNybpUM4gARs+DX9kDpGPTrZlLfJ Wedw1TXYUjQOTNwmtRbyZRS18lt8RT1AY4Y9rUFecvTqgUXlZiGhji0rna5VrYFWinDr UxGA== X-Gm-Message-State: AOAM533h/Bgtchcgq7Zx/n+IKSn88XCZHQ8tPrLNlYKV6r1mzhc20LIE 9LQtwv6rzyo964XrSrTIJOEbSMhkjs8C9Iixmu4= X-Google-Smtp-Source: ABdhPJyy7CDImDpVoI6smnphFzz0nshkkXfOM2GSP6v39hXPUf0ACqC5m/o6lV1oyWs6YUapLSQxaGKbAgI6/I6AhxA= X-Received: by 2002:adf:a74a:: with SMTP id e10mr17729wrd.185.1626110137854; Mon, 12 Jul 2021 10:15:37 -0700 (PDT) MIME-Version: 1.0 References: <1446990946.2994.192.camel@surprise> <83r1g3aady.fsf@gnu.org> <144d27f7-9486-0515-2ebd-4e8d9d9fc3b2@suse.cz> <4988937.164lfTNWpH@excalibur> <83k0lva2hv.fsf@gnu.org> In-Reply-To: <83k0lva2hv.fsf@gnu.org> From: Jonathan Wakely Date: Mon, 12 Jul 2021 18:15:26 +0100 Message-ID: Subject: Re: Benefits of using Sphinx documentation format To: Eli Zaretskii Cc: Matthias Kretz , "gcc@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2021 17:15:40 -0000 On Mon, 12 Jul 2021 at 18:04, Eli Zaretskii via Gcc wrote= : > > > From: Matthias Kretz > > Date: Mon, 12 Jul 2021 16:54:50 +0200 > > > > On Monday, 12 July 2021 16:30:23 CEST Martin Li=C5=A1ka wrote: > > > On 7/12/21 4:12 PM, Eli Zaretskii wrote: > > > > I get it that you dislike the HTML produced by Texinfo, but without > > > > some examples of such bad HTML it is impossible to know what exactl= y > > > > do you dislike and why. > > > > I believe Martin made a really good list. > > Gavin Smith, the GNU Texinfo maintainer, responded in detail to that > list. However, his message didn't get through to the list, for some > reason. It did: https://gcc.gnu.org/pipermail/gcc/2021-July/236744.html https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574987.html The HTML attachment has been stripped though. The relevant part of the HTML looks like this:
--greeting=3Dtext
-g text

Output text instead of the default greeting.

Note the anchor that is part of the
element, not the
(where the index-__002d anchor is still located). > Can someone please see why, and release his message? I think > he makes some important points, and his message does deserve being > posted and read as part of this discussion. He shows that some of the linking issues are addressed in the latest texinfo release, which is great. But it doesn't negate all Martin's other points. GCC devs and users who frequently modify or refer to the HTML docs want to replace texinfo. One vocal objector who just keeps repeating that texinfo is fine should not block that progress.