On Mon, 22 Apr 2024 at 22:30, Jakub Jelinek <ja...@redhat.com> wrote: > > Hi! > > I've run aspell on gcc.pot (just quickly skimming, so pressing > I key hundreds of times and just stopping when I catch something that > looks like a misspelling). > > I plan to commit this tomorrow as obvious unless somebody finds some > issues in it, you know, I'm not a native English speaker. > Yes, I know favour is valid UK spelling, but we spell the US way I think.
Yup: https://gcc.gnu.org/codingconventions.html#Spelling > I've left some *ise* -> *ize* cases (recognise, initialise), those > had too many hits, though in translatable strings just 4, so maybe > worth changing too: > msgid "recognise the specified suffix as a definition module filename" > msgid "recognise the specified suffix as implementation and module filenames" > "initialiser for a dylib." > msgid "%qE attribute argument %qE is not recognised" That spelling is explicitly mentioned at the link above, so they should be "ize" really. > 2024-04-22 Jakub Jelinek <ja...@redhat.com> > > * config/epiphany/epiphany.opt (may-round-for-trunc): Spelling fix: > floatig -> floating. > * config/riscv/riscv.opt (mcsr-check): Spelling fix: CRS -> CSR. > * params.opt (-param=ipa-cp-profile-count-base=): Spelling fix: > frequncy -> frequency. > gcc/c-family/ > * c.opt (Wstrict-flex-arrays): Spelling fix: inproper -> improper. > gcc/cp/ > * parser.cc (cp_parser_using_declaration): Spelling fix: favour > -> favor. > gcc/m2/ > * lang.opt (fuse-list=): Spelling fix: finalializations -> > finalizations. LGTM +Reviewed-by: Jonathan Wakely <jwak...@redhat.com>
