On Tuesday 21 March 2017 10:57:33 Florian Weimer wrote:
> On 03/17/2017 02:30 PM, David Malcolm wrote:
> > Paraphrasing myself from that RFE: given that many IDEs can already
> > parse LANG=C output, presumably you'd want a command-line flag that
> > suppresses just the translation of "error" and "
On Friday 17 March 2017 12:28:48 Jonathan Wakely wrote:
> On 17 March 2017 at 12:17, Frédéric Marchal wrote:
> > On Friday 17 March 2017 13:32:17 Janne Blomqvist wrote:
> >> Not my area of expertise, but it seems the Glorious Future (TM) in
> >> this area is something
On Friday 17 March 2017 09:30:40 David Malcolm wrote:
> This all sounds a lot like:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79423
That's exactly the problem I'm faced with. Thanks for pointing it out to me.
> Paraphrasing myself from that RFE: given that many IDEs can already
> parse L
On Friday 17 March 2017 13:32:17 Janne Blomqvist wrote:
> On Fri, Mar 17, 2017 at 10:48 AM, Frédéric Marchal
wrote:
> > This list certainly needs more thinking and IDE folks could give more
> > insight but you see were I'm heading.
>
> Not my area of expertise, but it
Hi,
I gave my partial French translation a field trial this week and it didn't went
well. QtCreator can't see error messages any more if they are translated.
QtCreator identifies errors and warnings by parsing gcc output:
file.c:24:5: error: …
file.c:25:3: warning: …
But if "error" and "warnin
