public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Gaius Mulley <gaiusmod2@gmail.com>,
	Arthur Cohen <arthur.cohen@embecosm.com>
Subject: [committed] Further spelling fixes in translatable strings
Date: Tue, 23 Apr 2024 14:57:11 +0200	[thread overview]
Message-ID: <ZiewJ7Fab4aAfCn+@tucnak> (raw)
In-Reply-To: <CACb0b4=O4nfDwehr9cp1Qeh-we-PwwpgQ4PSqhEvL_pLBsg9ow@mail.gmail.com>

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')
...
rust/parse/rust-parse-impl.h:               "unrecognised token %qs for item in trait",
rust/parse/rust-parse-impl.h:                "unrecognised token %qs for item in inherent impl",
but none of that making it into gcc.pot.

2024-04-23  Jakub Jelinek  <jakub@redhat.com>

	* config/darwin.opt (init): Spelling fix: initialiser -> initializer.
gcc/c-family/
	* c-attribs.cc (handle_objc_nullability_attribute): Spelling fix:
	recognised -> recognized.
gcc/m2/
	* lang.opt (fdef=, fmod=): Spelling fix: recognise -> recognize.

--- gcc/config/darwin.opt.jj	2024-01-03 11:51:43.137570111 +0100
+++ gcc/config/darwin.opt	2024-04-23 10:34:56.406196449 +0200
@@ -211,7 +211,7 @@ Driver RejectNegative Separate
 
 init
 Driver RejectNegative Separate
--init <symbol_name>	The symbol <symbol_name> will be used as the first initialiser for a dylib.
+-init <symbol_name>	The symbol <symbol_name> will be used as the first initializer for a dylib.
 
 install_name
 Driver RejectNegative Separate
--- gcc/c-family/c-attribs.cc.jj	2024-01-09 15:35:43.626688356 +0100
+++ gcc/c-family/c-attribs.cc	2024-04-23 10:30:23.458043442 +0200
@@ -6244,7 +6244,7 @@ handle_objc_nullability_attribute (tree
 	      || strcmp (TREE_STRING_POINTER (val), "resettable") == 0))
     *no_add_attrs = false; /* OK */
   else if (val != error_mark_node)
-    error ("%qE attribute argument %qE is not recognised", name, val);
+    error ("%qE attribute argument %qE is not recognized", name, val);
 
   return NULL_TREE;
 }
--- gcc/m2/lang.opt.jj	2024-04-23 08:30:59.312249288 +0200
+++ gcc/m2/lang.opt	2024-04-23 10:34:13.118806549 +0200
@@ -96,7 +96,7 @@ turn on tracing of procedure line number
 
 fdef=
 Modula-2 Joined
-recognise the specified suffix as a definition module filename
+recognize the specified suffix as a definition module filename
 
 fdump-system-exports
 Modula-2
@@ -172,7 +172,7 @@ compile all implementation modules and p
 
 fmod=
 Modula-2 Joined
-recognise the specified suffix as implementation and module filenames
+recognize the specified suffix as implementation and module filenames
 
 fnil
 Modula-2
@@ -278,7 +278,7 @@ static-libgm2
 Driver
 Link the standard Modula-2 libraries statically in the compilation.
 
-; Here are C options that we also recognise, either within the compiler
+; Here are C options that we also recognize, either within the compiler
 ; or to build the preprocessor command lines.
 
 Wall


	Jakub


  reply	other threads:[~2024-04-23 12:57 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   ` Jakub Jelinek [this message]
2024-04-24 14:25     ` [committed] Further spelling fixes in " Gaius Mulley

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=ZiewJ7Fab4aAfCn+@tucnak \
    --to=jakub@redhat.com \
    --cc=arthur.cohen@embecosm.com \
    --cc=gaiusmod2@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).