* [Bug translation/108890] Translation mistakes 2023
[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
` (4 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2023-02-23 9:05 UTC (permalink / raw)
To: gcc-rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://github.com/Rust-GCC
| |/gccrs/issues/1916
CC| |gcc-rust at gcc dot gnu.org,
| |tschwinge at gcc dot gnu.org
--- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
I've filed as *good-first-pr* <https://github.com/Rust-GCC/gccrs/issues/1916>
'Diagnostics and option help texts: GCC PR108890 "Translation mistakes 2023"'.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug translation/108890] Translation mistakes 2023
[not found] <bug-108890-35322@http.gcc.gnu.org/bugzilla/>
2023-02-23 9:05 ` [Bug translation/108890] Translation mistakes 2023 tschwinge at gcc dot gnu.org
@ 2023-02-23 9:24 ` jakub at gcc dot gnu.org
2023-02-23 10:36 ` jakub at gcc dot gnu.org
` (3 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2023-02-23 9:24 UTC (permalink / raw)
To: gcc-rust
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.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug translation/108890] Translation mistakes 2023
[not found] <bug-108890-35322@http.gcc.gnu.org/bugzilla/>
2023-02-23 9:05 ` [Bug translation/108890] Translation mistakes 2023 tschwinge at gcc dot gnu.org
2023-02-23 9:24 ` jakub at gcc dot gnu.org
@ 2023-02-23 10:36 ` jakub at gcc dot gnu.org
2023-02-23 14:28 ` cvs-commit at gcc dot gnu.org
` (2 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2023-02-23 10:36 UTC (permalink / raw)
To: gcc-rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612639.html
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612647.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug translation/108890] Translation mistakes 2023
[not found] <bug-108890-35322@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
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
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-02-23 14:28 UTC (permalink / raw)
To: gcc-rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:9f9a7095d910379cd86ac45f81c79b363f859996
commit r13-6304-g9f9a7095d910379cd86ac45f81c79b363f859996
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 23 15:27:31 2023 +0100
c++: Fix up -fcontracts option description [PR108890]
This translation PR mentioned the description is a little bit weird.
2023-02-23 Jakub Jelinek <jakub@redhat.com>
PR translation/108890
* c.opt (fcontracts): Fix description.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug translation/108890] Translation mistakes 2023
[not found] <bug-108890-35322@http.gcc.gnu.org/bugzilla/>
` (3 preceding siblings ...)
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
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-02-23 22:27 UTC (permalink / raw)
To: gcc-rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:7423f5b56ad436f51ac1b9defb954e2bdc5b06ab
commit r13-6307-g7423f5b56ad436f51ac1b9defb954e2bdc5b06ab
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 23 23:26:43 2023 +0100
xtensa: Fix up fatal_error message strings in xtensa-dynconfig.c [PR108890]
The translation PR complains that these 4 messages from xtensa-dynconfig.c
are marked in po/gcc.pot as c-format (which doesn't allow %qs) while they
should be gcc-internal-format.
The problem is in the manual translation of the strings with _(),
that should be both unnecessary because fatal_error invokes _() on its
argument already, but also incorrect for the above reason, for
gcc-internal-format strings one should use G_("...") instead if really
needed.
The following patch drops those _("..."), tested by regenerating po/gcc.pot
to see they are now gcc-internal-format, but not really tested on xtensa
target.
2023-02-23 Jakub Jelinek <jakub@redhat.com>
PR translation/108890
* config/xtensa/xtensa-dynconfig.c (xtensa_load_config): Drop _()s
around fatal_error format strings.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug translation/108890] Translation mistakes 2023
[not found] <bug-108890-35322@http.gcc.gnu.org/bugzilla/>
` (4 preceding siblings ...)
2023-02-23 22:27 ` cvs-commit at gcc dot gnu.org
@ 2024-01-16 17:39 ` cvs-commit at gcc dot gnu.org
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-01-16 17:39 UTC (permalink / raw)
To: gcc-rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890
--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Arthur Cohen <cohenarthur@gcc.gnu.org>:
https://gcc.gnu.org/g:747d9a92ddb74fa7ba1bb6ca0079abd5eaa38791
commit r14-7504-g747d9a92ddb74fa7ba1bb6ca0079abd5eaa38791
Author: TieWay59 <tieway59@foxmail.com>
Date: Wed Apr 19 14:07:34 2023 +0800
gccrs: Fix translation mistakes 2023 in GCC/Rust [PR108890]
In https://gcc.gnu.org/PR108890 "Translation mistakes 2023"
@rillig lists several issues with GCC/Rust diagnostics and
option help texts (but also a few non-GCC/Rust).
This commit fix mistakes only related to GCC/Rust,
specifically to the file `gcc/rust/lang.opt`.
closes https://github.com/Rust-GCC/gccrs/issues/1916
PR translation/108890
gcc/rust/
* lang.opt: Fix translation mistakes 2023 in
GCC/Rust [PR108890]
(line 67): change the inconsistent tab to spaces
(line 75): wrap bare placeholder `integer`
(line 79): remove redundant text of `Choose which`
(line 96): remove redundant text of `Choose which`
(line 112): remove redundant `Flag to`
(line 124): correct the exclusive term `When to stop`
(line 124): correct typo of `copimlation`
Signed-off-by: Tieway59 <tieway59@foxmail.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread