public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109309] Untranslated text in diagnostic Date: Tue, 28 Mar 2023 15:50:50 +0000 [thread overview] Message-ID: <bug-109309-4-ypm9IfPdH9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109309-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109309 --- Comment #2 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:af45b17d0a8fe3e7ae08662008a1f41e48a4a3eb commit r13-6911-gaf45b17d0a8fe3e7ae08662008a1f41e48a4a3eb Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Mar 28 17:49:23 2023 +0200 c++: Allow translations of check_postcondition_result messages [PR109309] As mentioned in the PR, constructing a message from two parts by concatenating them prevents translations, unless one of the parts is a keyword which should be never translated. The following patch fixes that. 2023-03-28 Jakub Jelinek <jakub@redhat.com> PR c++/109309 * contracts.cc: Include intl.h. (check_postcondition_result): Don't form diagnostics from two halves of an English message to allow translations.
next prev parent reply other threads:[~2023-03-28 15:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-28 4:05 [Bug c++/109309] New: " roland.illig at gmx dot de 2023-03-28 7:25 ` [Bug c++/109309] " rguenth at gcc dot gnu.org 2023-03-28 13:14 ` redi at gcc dot gnu.org 2023-03-28 15:50 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-28 15:52 ` jakub 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-109309-4-ypm9IfPdH9@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).