From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fencepost.gnu.org (fencepost.gnu.org [IPv6:2001:470:142:3::e]) by sourceware.org (Postfix) with ESMTPS id DBA42385743A; Mon, 12 Jul 2021 17:09:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DBA42385743A Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4277 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m2zRH-0005c4-6q; Mon, 12 Jul 2021 13:09:51 -0400 Date: Mon, 12 Jul 2021 20:09:46 +0300 Message-Id: <83im1fa279.fsf@gnu.org> From: Eli Zaretskii To: Martin =?utf-8?Q?Li=C5=A1ka?= Cc: jwakely.gcc@gmail.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org, joseph@codesourcery.com In-Reply-To: <3bf99357-7b22-47a8-a7b9-e83a97b954e3@suse.cz> (message from Martin =?utf-8?Q?Li=C5=A1ka?= on Mon, 12 Jul 2021 16:34:11 +0200) Subject: Re: Benefits of using Sphinx documentation format References: <1446990946.2994.192.camel@surprise> <5ffe3e32-ece0-a1b4-1fcf-e35177fa80b5@suse.cz> <87489d9a-44e2-411c-3f3a-534d07e78b95@suse.cz> <0866a0ea-c846-ea5e-ac7a-d1c8f106cc45@suse.cz> <5bb9a10d-f3b9-f16a-7430-bbae2d4978e2@suse.cz> <2f60f602-5d88-7674-9620-2172748664c5@suse.cz> <83a6n8obh4.fsf@gnu.org> <57743e51-04d5-ec2e-b684-54f0321ef0bd@suse.cz> <83pmw3mrcg.fsf@gnu.org> <98388e12-3712-575b-9387-45b6ea7ef498@suse.cz> <83v95fabwx.fsf@gnu.org> <83pmvnaa8g.fsf@gnu.org> <3bf99357-7b22-47a8-a7b9-e83a97b954e3@suse.cz> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: ** 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:09:52 -0000 > Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org, joseph@codesourcery.com > From: Martin Liška > Date: Mon, 12 Jul 2021 16:34:11 +0200 > > > "Texinfo must go" is one possible conclusion from your description. > > But it isn't the only one. An alternative is "the Texinfo source of > > the GCC manual must be improved to fix this problem." And yes, this > > problem does have a solution in Texinfo. > > No, the alternative is more powerful output given by Texinfo, in particular > more modern HTML pages. Please see the response by Gavin: it sounds like at least some of that was resolved in Texinfo, sometimes long ago.