public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34729]  New: Localization of run-time error messages, written into the executable
Date: Thu, 10 Jan 2008 15:09:00 -0000	[thread overview]
Message-ID: <bug-34729-13404@http.gcc.gnu.org/bugzilla/> (raw)

I saw that gfortran writes (at least sometimes) a localized run-time error
message:

_gfortran_runtime_error (&"Attempt to allocate a negative amount of
memory."[1]{lb: 1 sz: 1});
_gfortran_os_error (&"Memory allocation failed"[1]{lb: 1 sz: 1});

becomes then (LANG=de_DE.UTF-8):

_gfortran_runtime_error (&"Versuch, einen negativen Betrag von Speicher zu
r"[1]{lb: 1 sz: 1});
_gfortran_os_error (&"Speicherreservierung gesc"[1]{lb: 1 sz: 1});

The first string should be:
"Versuch, einen negativen Betrag von Speicher zu reservieren."
and the second
"Speicherreservierung gescheitert"
one sees that the strings are truncated.

Expected:
Either the localized message should not be truncated - or the English version
of the string should be used throughout.


-- 
           Summary: Localization of run-time error messages, written into
                    the executable
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34729


             reply	other threads:[~2008-01-10 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 15:09 burnus at gcc dot gnu dot org [this message]
2008-02-01 13:59 ` [Bug fortran/34729] " fxcoudert at gcc dot gnu dot org
2008-02-01 14:23 ` fxcoudert at gcc dot gnu dot org
2008-02-25  8:37 ` fxcoudert at gcc dot gnu dot org
2008-02-25  8:38 ` fxcoudert at gcc dot gnu dot 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-34729-13404@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: 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).