This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug translation/40872] String not extracted for translation
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Nov 2009 13:26:30 -0000
- Subject: [Bug translation/40872] String not extracted for translation
- References: <bug-40872-10888@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #21 from joseph at codesourcery dot com 2009-11-13 13:26 -------
Subject: Re: String not extracted for translation
On Fri, 13 Nov 2009, pearly dot zhao at oracle dot com wrote:
> (In reply to comment #19)
> > Subject: Re: String not extracted for translation
> >
> > It didn't do so when I last ran it (gettext 0.17). Are you using another
> > version? Maybe there need to be stricter version requirements on gettext?
> >
> You are right. When I ran with gettext 0.17, only the first string of
> conditional string can be pick up for translation. But I have run with gettext
> 0.14.6 before. It can extracted both the conditional expression strings for
> translation.
> So do the codes need match with the latest gettext and improve the version
> warning to xgettext at exgettext?
One possibility would certainly be to improve the current development
version of gettext, get a new release out, and then require the new
version (or later) in exgettext and install.texi. That supposes this was
not a deliberate change in gettext but a bug that can be safely fixed
there.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40872