From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 780FC382FE4B for ; Tue, 28 Jun 2022 12:11:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 780FC382FE4B Received: from fencepost.gnu.org ([2001:470:142:3::e]:57588) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6A1x-0003t7-2P; Tue, 28 Jun 2022 08:09:21 -0400 Received: from [87.69.77.57] (port=3153 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 1o6A1w-0005lB-E0; Tue, 28 Jun 2022 08:09:20 -0400 Date: Tue, 28 Jun 2022 15:09:24 +0300 Message-Id: <83pmit6lcb.fsf@gnu.org> From: Eli Zaretskii To: Pedro Alves Cc: felix.willgerodt@intel.com, gdb-patches@sourceware.org In-Reply-To: (message from Pedro Alves on Mon, 27 Jun 2022 20:15:17 +0100) Subject: Re: [PATCH 2/4] gdb, gdbserver: Add AMX registers. References: <20220506121226.137608-1-felix.willgerodt@intel.com> <20220506121226.137608-3-felix.willgerodt@intel.com> <834k2226ht.fsf@gnu.org> <834k1ws3d3.fsf@gnu.org> <83y1xi6k22.fsf@gnu.org> X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2022 12:11:36 -0000 > Date: Mon, 27 Jun 2022 20:15:17 +0100 > Cc: felix.willgerodt@intel.com, gdb-patches@sourceware.org > From: Pedro Alves > > Given the manual is written in US English, I wonder why we let locale influence > sorting order. I mean, shouldn't we be forcing locale to LANC=C or some such when > generating the manual, to be sure the sections are always sorted the same way? Doing this means we cannot include any non-ASCII text in the manual, ever. Not even mention names of people whose names include non-ASCII characters. Also, I think doing that means the Unicode characters produced by makeinfo from the likes of @result, @print, @error, etc. will be replaced by their ASCII equivalents -- do we really want that? In sum, this would be an unusual thing to do, as GNU manuals go. There is actually in recent years an urge to produce UTF-8 encoded manuals, not go back to plain ASCII. > (At least the html manual sorts the concept index ignoring case for me, and I see > the same in the docs copy in the gdb website, so I assume that's the order we want.) The purpose of this convention to let everyone produce a manual with the same order, regardless of the locale in which the manual is produced. That manuals on the site, which are produced in en_US, do TRT doesn't surprise me at all... The burden in practice is not too heavy, since only a handful of our index entries use company names (or any proper names, for that matter).