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/29711] error_print does not support %N$X
Date: Tue, 14 Nov 2006 17:16:00 -0000	[thread overview]
Message-ID: <20061114171639.1587.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29711-13404@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]



------- Comment #5 from burnus at gcc dot gnu dot org  2006-11-14 17:16 -------
> Fehler: Bei (1) referenziertes Symbol »bar« nicht im Modul »foo« gefunden
>
> My limited german knowledge seems to indicate that it's OK, but I'm not sure.
Looks ok.

> Could you try the attached patch on a few cases (possibly including multiple
> loci and such arguments reorganizations)?

I will try. It actually effects the following strings in the following
languages (see gcc/po/):

de.po-msgid "Symbol '%s' referenced at %L not found in module '%s'"
de.po-msgid "User operator '%s' referenced at %L not found in module '%s'"
de.po-msgid "Intrinsic operator '%s' referenced at %L not found in module '%s'"
de.po-msgid "The equivalence set for variable '%s' declared at %L violates
alignment requirents"

tr.po-msgid "Processing spec %c%s%c, which is '%s'\n"
tr.po:msgstr "'%4$s' %1$c%2$s%3$c ozelligi isleniyor\n"
^ This could be a challenge!
tr.po-msgid "%s: warning: using formals list from %s(%d) for function '%s'\n"
tr.po-msgid "collect: tweaking %s in %s\n"

zh_TW.po-msgid "Assumed size array '%s' in namelist '%s'at %C is not allowed."
zh_TW.po-msgid "Assumed shape array '%s' in namelist '%s' at %C is an
extension."
zh_TW.po-msgid "Argument '%s' of pure function '%s' at %L must be INTENT(IN)"

(Reminder to self: test also "%s does not support %%n$ operand number
formats".)


-- 


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


  parent reply	other threads:[~2006-11-14 17:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-04 13:28 [Bug fortran/29711] New: error_print produces useless error message for LANG != C burnus at gcc dot gnu dot org
2006-11-04 13:28 ` [Bug fortran/29711] " burnus at gcc dot gnu dot org
2006-11-04 17:22 ` [Bug fortran/29711] error_print does not support %N$X pinskia at gcc dot gnu dot org
2006-11-14 10:39 ` fxcoudert at gcc dot gnu dot org
2006-11-14 16:44 ` fxcoudert at gcc dot gnu dot org
2006-11-14 16:45 ` fxcoudert at gcc dot gnu dot org
2006-11-14 17:16 ` burnus at gcc dot gnu dot org [this message]
2006-11-19 18:19 ` burnus at gcc dot gnu dot org
2006-11-25 16:57 ` fxcoudert at gcc dot gnu dot org
2006-11-25 17:00 ` [Bug fortran/29711] [4.2 only] " fxcoudert at gcc dot gnu dot org
2006-12-06 20:14 ` burnus at gcc dot gnu dot org
2006-12-06 22:59 ` burnus at gcc dot gnu dot org
2006-12-07  0:06 ` patchapp at dberlin dot org
2006-12-07  9:16 ` burnus at gcc dot gnu dot org
2006-12-11 20:58 ` fxcoudert at gcc dot gnu dot org
2006-12-11 20:58 ` 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=20061114171639.1587.qmail@sourceware.org \
    --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).