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: "manu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Jul 2009 16:55:08 -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 #3 from manu at gcc dot gnu dot org 2009-07-27 16:55 -------
(In reply to comment #2)
> I tried to look for more similar cases. But I couldn't find anything. Not
> that it is all that easy to search for. Neither "error" nor "?" are
> particularly good search terms. :-) So I may very well have missed something.
Try grep -e ' error ([^"]' gcc/*.c -A 1
I am sure you can come up with smart regexp for warning, warning_at, error_at,
inform and the other diagnostic functions.
> Previously, I have reported a couple of instances where things can't be
> properly translated. But that has mostly been cases where the code needs a
> small rewrite. I'm not sure how to "commonize" those; they typically have to
> be handled case-by-case.
In this case, the string just have to be surrounded by G_() so:
error (funcdef_flag
? G_("%qs defined in a non-class scope")
: G_("%qs declared in a non-class scope"), name);
Care to contribute a patch for this and other cases?
Thanks,
Manuel.
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Component|c++ |translation
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-07-27 16:55:08
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40872