public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug translation/104552] Mistakes in strings to be translated in GCC 12 Date: Tue, 08 Mar 2022 17:45:46 +0000 [thread overview] Message-ID: <bug-104552-4-Jrcjw5iOST@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104552-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #33 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- (In reply to Eric Gallager from comment #28) > (In reply to Roland Illig from comment #10) > > From aarch64-sve-builtins.cc: > > > error_at (location, "passing single vector %qT to argument %d" > > > " of %qE, which expects a tuple of %d vectors", > > > actual, argno + 1, fndecl, num_vectors); > > > > "%d vectors" must use the correct plural form, for the benefit of Polish, > > Russian, Arabic and several more. > > Richard Sandiford's string (624d0f07) OK, will fix. > (In reply to Roland Illig from comment #11) > > From aarch64-sve-builtins.cc: > > > passing %qT to argument %d of %qE, which expects a scalar integer > > > > "scalar integer" sounds redundant, this may be a copy-and-paste mistake from > > the message directly above, which says "scalar element". > > Likewise. I think it's worth keeping, at least in English. The error could otherwise end up being something like: passing “svint32_t” to argument 2 of foo, which expects an integer which IMO isn't as obvious: the crucial scalar vs. vector distinction is now implicit rather than explicit. > (In reply to Roland Illig from comment #12) > > From aarch64-sve-builtins.cc: > > > "capture by copy of SVE type %qT" > > > > This message should use the same grammar as the related ones, the word > > "cannot" is a useful indicator of the general error condition. > > Same author, different commit (02a32ab4) This follows the style of the corresponding error for incomplete types (cp/lambda.cc:add_capture). It seems OK to me, so I'd prefer to keep it for consistency. The “cannot” errors are for actions like new, delete and throw, so I think saying “the program cannot do this” makes sense there. But IMO it's at least borderline whether lambda captures are declarative or imperative. IMO they're more akin to parameter declarations. > (In reply to Roland Illig from comment #14) > > From aarch64.cc: > > > "invalid name (%qs) in %<target(\"arch=\")%> pragma or attribute" > > > > What is the point of having parentheses around %qs? That seems redundant to > > me. Not my string, but I quite like the parentheses TBH. :-) Translations don't need to keep them if they aren't natural for the target language.
next prev parent reply other threads:[~2022-03-08 17:45 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-15 18:17 [Bug translation/104552] New: " roland.illig at gmx dot de 2022-02-15 18:21 ` [Bug translation/104552] " redi at gcc dot gnu.org 2022-02-15 18:40 ` ibuclaw at gdcproject dot org 2022-02-15 18:49 ` roland.illig at gmx dot de 2022-02-17 21:03 ` roland.illig at gmx dot de 2022-02-17 21:18 ` schwab@linux-m68k.org 2022-02-17 21:27 ` redi at gcc dot gnu.org 2022-02-24 20:12 ` roland.illig at gmx dot de 2022-03-01 1:57 ` egallager at gcc dot gnu.org 2022-03-03 23:09 ` roland.illig at gmx dot de 2022-03-04 20:41 ` roland.illig at gmx dot de 2022-03-04 20:52 ` roland.illig at gmx dot de 2022-03-04 21:03 ` roland.illig at gmx dot de 2022-03-04 21:13 ` roland.illig at gmx dot de 2022-03-04 21:23 ` roland.illig at gmx dot de 2022-03-04 21:25 ` roland.illig at gmx dot de 2022-03-04 21:27 ` roland.illig at gmx dot de 2022-03-04 21:31 ` roland.illig at gmx dot de 2022-03-04 21:57 ` roland.illig at gmx dot de 2022-03-04 22:29 ` roland.illig at gmx dot de 2022-03-04 22:33 ` roland.illig at gmx dot de 2022-03-04 22:36 ` roland.illig at gmx dot de 2022-03-04 22:48 ` roland.illig at gmx dot de 2022-03-05 21:17 ` roland.illig at gmx dot de 2022-03-05 21:24 ` roland.illig at gmx dot de 2022-03-06 21:48 ` roland.illig at gmx dot de 2022-03-06 21:51 ` roland.illig at gmx dot de 2022-03-06 21:59 ` roland.illig at gmx dot de 2022-03-07 17:40 ` egallager at gcc dot gnu.org 2022-03-07 19:03 ` egallager at gcc dot gnu.org 2022-03-08 0:01 ` egallager at gcc dot gnu.org 2022-03-08 10:48 ` cvs-commit at gcc dot gnu.org 2022-03-08 12:31 ` marxin at gcc dot gnu.org 2022-03-08 17:18 ` cvs-commit at gcc dot gnu.org 2022-03-08 17:45 ` rsandifo at gcc dot gnu.org [this message] 2022-03-08 19:30 ` cvs-commit at gcc dot gnu.org 2022-03-09 0:26 ` roland.illig at gmx dot de 2022-03-11 22:36 ` cvs-commit at gcc dot gnu.org 2022-03-12 15:08 ` roland.illig at gmx dot de 2022-03-12 22:27 ` roland.illig at gmx dot de 2022-03-13 3:21 ` egallager at gcc dot gnu.org 2022-03-13 18:20 ` roland.illig at gmx dot de 2022-03-22 12:51 ` marxin at gcc dot gnu.org 2022-03-22 12:54 ` marxin at gcc dot gnu.org 2022-04-05 16:40 ` rsandifo at gcc dot gnu.org
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=bug-104552-4-Jrcjw5iOST@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).