public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9390: Segmentation Fault when compiling for athlon with LANG=es_ES@euro or LC_ALL=es_ES@euro Date: Sun, 02 Feb 2003 19:36:00 -0000 [thread overview] Message-ID: <20030202193600.19499.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9390; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: "Joseph S. Myers" <jsm28@cam.ac.uk> Cc: david@aspl.es, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c/9390: Segmentation Fault when compiling for athlon with LANG=es_ES@euro or LC_ALL=es_ES@euro Date: Sun, 2 Feb 2003 13:28:08 -0600 (CST) > > State-Changed-From-To: open->closed > > State-Changed-By: bangerth > > Another one of these nasty translation problems. The > > translation files are wrong, with some messages using more > > or less parameters than the english original. This leads to > > the ICE. > > > > We need to get methods in place to check for this... > > > > Sorry, there is not much that we can do about it for now. > > Translation bugs are still bugs in GCC, although they need to be forwarded > to the relevant language team to be fixed. They should not be closed in > the GCC bug database until fixed in GCC (i.e., until the new .po file is > in GCC CVS). Has such a .po file been committed? Have you forwarded the > report to the relevant translation team? Well, I am happy to reopen this if you insist. However, there is a more structural problem, which will not be solved by just finding out the one message that caused the ICE here, so I don't think there is much value in just fixing this one. The problem is thet we have tons of messages like "Don't do %X with %Y using %Z" and translations like "Versuch %X mit %Z zu tun" Here, the number of %-sequences don't match, which leads to the ICE. I had identified this sometime back last November (+- 1 month; see the mailing list archives), and a quick scan showed that we literally hundreds of these cases. We need to have a process that prevents this up front. Just fixing individual messages is not sufficient. With respect to this particular case: we already have at least one prototypical report about this open. I closed this one as kind-of-a- duplicate. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-02-02 19:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-02 19:36 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-05 0:06 Wolfgang Bangerth 2003-02-04 23:46 Joseph S. Myers 2003-02-03 16:16 Wolfgang Bangerth 2003-02-03 0:06 Joseph S. Myers 2003-02-01 23:36 Joseph S. Myers 2003-02-01 22:16 bangerth 2003-01-21 18:06 david
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=20030202193600.19499.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).