From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5517 invoked by alias); 16 Oct 2009 15:31:18 -0000 Received: (qmail 4622 invoked by uid 48); 16 Oct 2009 15:31:00 -0000 Date: Fri, 16 Oct 2009 15:31:00 -0000 Subject: [Bug lto/41731] New: The linker plugin should support translations X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "espindola at google dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-10/txt/msg01466.txt.bz2 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