From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug translation/108890] Translation mistakes 2023
Date: Thu, 23 Feb 2023 09:24:19 +0000 [thread overview]
Message-ID: <bug-108890-35322-P9kId5WE37@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108890-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gaius at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Roland Illig from comment #0)
> > %qs is loaded but symbol %qs is not found: %s
>
> That string is marked as 'format-c' but should be 'format-gcc-internal'.
This is xtensa-dynconfig.c (and there are other strings from it too).
I wonder if this isn't because the file is still named *.c rather than *.cc,
otherwise
no ideas. Because the messages are in fatal_error...
> > to generate dependencies you must specify '-fcpp'
>
> Trailing whitespace, wrong quotes.
This is in m2 FE.
> > Enable certain features present drafts of C++ Contracts.
>
> Grammar?
This one is C++, rest is Rust.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-23 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-108890-35322@http.gcc.gnu.org/bugzilla/>
2023-02-23 9:05 ` tschwinge at gcc dot gnu.org
2023-02-23 9:24 ` jakub at gcc dot gnu.org [this message]
2023-02-23 10:36 ` jakub at gcc dot gnu.org
2023-02-23 14:28 ` cvs-commit at gcc dot gnu.org
2023-02-23 22:27 ` cvs-commit at gcc dot gnu.org
2024-01-16 17:39 ` cvs-commit 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-108890-35322-P9kId5WE37@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@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: 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).