public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52279] New: Fortran translation issues issues
Date: Thu, 16 Feb 2012 14:29:00 -0000	[thread overview]
Message-ID: <bug-52279-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52279
           Summary: Fortran translation issues issues
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org
            Blocks: 52274


A) gfc_check_conformance - but possibly others - have:

  if (gfc_check_conformance (op1, op2,
                             "elemental binary operation") != SUCCESS)

and then in gfc_check_conformance:
          gfc_error ("Different shape for %s at %L on dimension %d "
                     "(%d and %d)", _(buffer), &op1->where, d + 1,

There are two issues: The passed string is not marked as to be translated. One
should use "G_()" [non-std-C string], N_(), or _(). And translating

"Different shape for "                 " at %L on dimension %d"
               "elemental binary operation"

properly is difficult without the context.


B) gfc_check_intrinsic_standard

    case GFC_STD_F95:
      symstd_msg = "new in Fortran 95";
...
        gfc_warning ("Intrinsic '%s' (is %s) is used at %L",
                     isym->name, _(symstd_msg), &where);

Again, the symstd_msg text does not end up in the .pot file. Additionally,
translating  "(is %s)" is rather difficult. At least the 'is ' should moved
into symstd_msg; possibly the whole string. [For the latter: Be careful that
"%s" etc. still get expanded correctly.]


C) There are probably some more such items.

D) In some cases, giving translation hints would help translators.


             reply	other threads:[~2012-02-16 14:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 14:29 burnus at gcc dot gnu.org [this message]
2013-06-29 22:24 ` [Bug fortran/52279] " dominiq at lps dot ens.fr
2020-07-01 16:08 ` [Bug fortran/52279] Fortran translation issues cvs-commit at gcc dot gnu.org
2020-07-01 21:39 ` kargl at gcc dot gnu.org
2020-07-02 10:05 ` cvs-commit at gcc dot gnu.org
2020-07-02 10:14 ` markeggleston at gcc dot gnu.org
2020-07-02 10:39 ` markeggleston at gcc dot gnu.org
2020-07-02 15:31 ` kargl at gcc dot gnu.org
2020-07-02 15:53 ` jakub at gcc dot gnu.org
2020-07-02 16:41 ` sgk at troutmask dot apl.washington.edu
2020-07-02 17:10 ` schwab@linux-m68k.org
2020-07-02 17:15 ` sgk at troutmask dot apl.washington.edu
2020-07-02 17:24 ` schwab@linux-m68k.org
2020-07-02 18:41 ` sgk at troutmask dot apl.washington.edu
2021-11-03 20:19 ` egallager 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-52279-4@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).