From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Vladimir Prus'" <vladimir@codesourcery.com>
Cc: <tromey@redhat.com>,
"'Thiago Jung Bauermann'" <bauerman@br.ibm.com>,
<gdb-patches@sourceware.org>
Subject: RE: TR: ARI warning list change Fri May 29 01:53:26 UTC 2009
Date: Fri, 29 May 2009 08:32:00 -0000 [thread overview]
Message-ID: <000601c9e037$de6565a0$9b3030e0$@u-strasbg.fr> (raw)
In-Reply-To: <200905291140.18693.vladimir@codesourcery.com>
> > Objet : ARI warning list change Fri May 29 01:53:26 UTC 2009
> >
> > 657a658,659
> > > gdb/mi/mi-cmd-var.c:251: gettext: _ markup: All messages should be
> marked
> I am missing context on this email, but at least in MI, it's not yet
> clear
> which messages should be i18n and which are not. Some are results of
> frontend
> coding bug and as such should be never presented to user and should not
> be
> ever translated. And if they are translated, they won't help the user
> but
> will make it harder to understand the error for developer.
You are probably right... I don't know much about mi...
Should this warning disappear for mi directory altogether,
or should we add a /* ARI: _ markup */ to silence gdb_ari.sh
where translation is discouraged?
Pierre
PS: Could you take care of the missing "_()"
in gdb/varobj.c source?
I think that these are the kind of patches that can go in
as obvious, as all mechanical ARI fixes.
I hope that I translated correctly here my
remembering of discussions that we had about this.
next prev parent reply other threads:[~2009-05-29 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 6:52 Pierre Muller
2009-05-29 7:40 ` Vladimir Prus
2009-05-29 8:32 ` Pierre Muller [this message]
2009-05-29 9:09 ` Vladimir Prus
2009-05-29 9:43 ` Pierre Muller
2009-06-08 1:31 ` Thiago Jung Bauermann
2009-06-05 18:53 ` Tom Tromey
2009-06-05 19:43 ` Tom Tromey
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='000601c9e037$de6565a0$9b3030e0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=vladimir@codesourcery.com \
/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