From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] gdb, gdbserver: Add AMX registers.
Date: Tue, 28 Jun 2022 15:09:24 +0300 [thread overview]
Message-ID: <83pmit6lcb.fsf@gnu.org> (raw)
In-Reply-To: <d6ebcd3a-33b5-ffb2-f53f-ae1322f2e98f@palves.net> (message from Pedro Alves on Mon, 27 Jun 2022 20:15:17 +0100)
> Date: Mon, 27 Jun 2022 20:15:17 +0100
> Cc: felix.willgerodt@intel.com, gdb-patches@sourceware.org
> From: Pedro Alves <pedro@palves.net>
>
> 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).
next prev parent reply other threads:[~2022-06-28 14:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 12:12 [PATCH 0/4] Add AMX support Felix Willgerodt via Gdb-patches
2022-05-06 12:12 ` [PATCH 1/4] gdb: define int512 and uint512 as built-in types Felix Willgerodt via Gdb-patches
2022-05-06 12:19 ` Eli Zaretskii via Gdb-patches
2022-06-27 18:17 ` Pedro Alves
2022-05-06 12:12 ` [PATCH 2/4] gdb, gdbserver: Add AMX registers Felix Willgerodt via Gdb-patches
2022-05-06 12:25 ` Eli Zaretskii via Gdb-patches
2022-05-11 8:14 ` Willgerodt, Felix via Gdb-patches
2022-05-11 11:41 ` Eli Zaretskii via Gdb-patches
2022-06-27 18:16 ` Pedro Alves
2022-06-27 18:24 ` Eli Zaretskii via Gdb-patches
2022-06-27 19:15 ` Pedro Alves
2022-06-28 12:09 ` Eli Zaretskii via Gdb-patches [this message]
2022-06-28 13:35 ` Pedro Alves
2022-05-06 16:17 ` John Baldwin
2022-05-09 7:04 ` Willgerodt, Felix via Gdb-patches
2022-05-09 16:31 ` John Baldwin
2022-06-27 18:12 ` Pedro Alves
2022-07-14 10:54 ` Willgerodt, Felix via Gdb-patches
2022-07-15 11:51 ` Willgerodt, Felix via Gdb-patches
2022-08-08 9:15 ` Willgerodt, Felix via Gdb-patches
2022-08-08 17:16 ` John Baldwin
2022-05-06 12:12 ` [PATCH 3/4] gdb, gdbserver: Allocate only a sane amount of buffer when fetching registers Felix Willgerodt via Gdb-patches
2022-05-06 16:08 ` John Baldwin
2022-05-09 7:04 ` Willgerodt, Felix via Gdb-patches
2022-06-27 18:30 ` Pedro Alves
2022-05-06 12:12 ` [PATCH 4/4] gdb: Clear tilecfg.start_row for any PC modification Felix Willgerodt via Gdb-patches
2022-06-27 18:55 ` Pedro Alves
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pmit6lcb.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=pedro@palves.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox