From: Gaius Mulley <gaiusmod2@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
gcc-patches@gcc.gnu.org,
Arthur Cohen <arthur.cohen@embecosm.com>
Subject: Re: [committed] Further spelling fixes in translatable strings
Date: Wed, 24 Apr 2024 15:25:43 +0100 [thread overview]
Message-ID: <87il06q1lk.fsf@localhost> (raw)
In-Reply-To: <ZiewJ7Fab4aAfCn+@tucnak> (Jakub Jelinek's message of "Tue, 23 Apr 2024 14:57:11 +0200")
Jakub Jelinek <jakub@redhat.com> writes:
> On Tue, Apr 23, 2024 at 11:32:08AM +0100, Jonathan Wakely wrote:
>> On Mon, 22 Apr 2024 at 22:30, Jakub Jelinek <jakub@redhat.com> wrote:
>> Yup:
>> https://gcc.gnu.org/codingconventions.html#Spelling
>>
>> That spelling is explicitly mentioned at the link above, so they
>> should be "ize" really.
>
> Ok. I've committed that patch plus the following as obvious too.
>
> I see various similar cases in m2 and rust FEs where they don't make it into
> gcc/po/gcc.pot, guess those would be nice to get fixed too, end best even find out
> how to make those messages translatable.
> Talking about e.g.
> m2/gm2-compiler/M2Quads.mod: '%a unrecognised builtin constant', Id) |
> m2/gm2-compiler/M2Quads.mod: InternalError ('unrecognised value')
many thanks for spotting these errors - I'll look into getting the
messages translatable,
regards,
Gaius
prev parent reply other threads:[~2024-04-24 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 21:30 [PATCH] Spelling fixes for " Jakub Jelinek
2024-04-22 22:11 ` Palmer Dabbelt
2024-04-23 10:32 ` Jonathan Wakely
2024-04-23 12:57 ` [committed] Further spelling fixes in " Jakub Jelinek
2024-04-24 14:25 ` Gaius Mulley [this message]
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=87il06q1lk.fsf@localhost \
--to=gaiusmod2@gmail.com \
--cc=arthur.cohen@embecosm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jwakely@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).