https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90118
--- Comment #5 from Roland Illig <roland.illig at gmx dot de> ---
(In reply to Christophe Lyon from comment #3)
> When running the script, it warned in 3 more occurrences in gcc/cp/call.c,
> which I updated too.
By reading the code, I think these instances are correct since the trailing
space is added by this code:
const char *msg = (msgstr == NULL
? ""
: ACONCAT ((msgstr, " ", NULL)));
There's a much worse problem regarding the first %s though, which I have just
reported in bug 90152.
It would be good if the check-internal-format-escaping.py linter would actually
output what is wrong in the msgid. The number of checks will increase as I'm
trying to translate the rest of GCC 9, therefore it will become more difficult
to guess what is wrong with a translation. Ideally this linter should follow
the GCC guidelines for diagnostics, which are described in
https://gcc.gnu.org/onlinedocs/gccint/Guidelines-for-Diagnostics.html.
