public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "espindola at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/41731]  New: The linker plugin should support translations
Date: Fri, 16 Oct 2009 15:31:00 -0000	[thread overview]
Message-ID: <bug-41731-16169@http.gcc.gnu.org/bugzilla/> (raw)

Joseph S. Myers says:

Is this callback interface defined to take translated or untranslated
text?  If untranslated, there would be a problem with the callback knowing
which textual domain to use for translation, so I'd guess it should be
defined to take translated messages.  This means you should be translating
the messages first, using dgettext to use the right domain (which I think
should be "gcc" rather than inventing yet another domain for a few
messages).  You also need to call bindtextdomain - see how cpplib does
things for an example of one domain being used in a library in a program
that mainly uses another domain (cpplib and gcc there, gcc and whatever
domain the linker uses - it appears to be "gold" - here).  Then
gcc/po/exgettext needs to get the messages extracted for translation into
gcc/po/gcc.pot.


-- 
           Summary: The linker plugin should support translations
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: espindola at google dot com
 GCC build triplet: x86_64-linux-gnu
  GCC host triplet: x86_64-linux-gnu
GCC target triplet: x86_64-linux-gnu


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


                 reply	other threads:[~2009-10-16 15:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-41731-16169@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).