Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't give spurious warnings when using thread specific breakpoints
Date: Fri, 20 Oct 2006 06:10:00 -0000	[thread overview]
Message-ID: <uac3rqzz6.fsf@gnu.org> (raw)
In-Reply-To: <45374981.5080304@st.com> (message from Andrew STUBBS on Thu, 19 	Oct 2006 10:46:41 +0100)

> Date: Thu, 19 Oct 2006 10:46:41 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb-patches@sourceware.org
> 
> Of course, if they are translating without any reference to the context 
> in which it is displayed, and without being programmers, then I suspect 
> the translation would read rather like a Chinese road sign.

As I wrote, most translators are not programmers, and should not be
required to read the code.  It is best if the message phrase speaks
for itself; if not, gettext lets you put the explanation of the
context into specially-formatted comments that are copied into the
message catalog next to the message itself.  The translators will then
realize the context from those comments.

> No, you misunderstand the code. There can be an arbitrary number 
> breakpoints, each of which can have zero, one or two annotations, and 
> they are all presented as one message.

I was trying to give an example, so the question is: did I succeed to
explain how to resolve these issues?  If not, please show me several
examples of the output that this code produces now, and I will modify
my counter-example accordingly.

TIA


  reply	other threads:[~2006-10-20  6:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 13:44 Andrew STUBBS
2006-10-11 13:55 ` Daniel Jacobowitz
2006-10-11 14:46   ` Andrew STUBBS
2006-10-11 20:45     ` Daniel Jacobowitz
2006-10-11 22:12       ` Mark Kettenis
2006-10-11 22:14       ` Joel Brobecker
2006-10-18 12:01       ` Andrew STUBBS
2006-10-18 14:14         ` Daniel Jacobowitz
2006-10-18 15:12           ` Andrew STUBBS
2006-10-18 19:47             ` Eli Zaretskii
2006-10-18 20:21               ` Andreas Schwab
2006-10-19  4:17                 ` Eli Zaretskii
2006-10-19  9:47               ` Andrew STUBBS
2006-10-20  6:10                 ` Eli Zaretskii [this message]
2006-10-20 14:29                   ` Daniel Jacobowitz
2006-10-20 17:42                     ` Eli Zaretskii
2006-10-20 17:47                       ` Daniel Jacobowitz
2006-10-20 18:03                         ` Eli Zaretskii
2006-10-20 18:07                           ` Daniel Jacobowitz
2006-10-20 18:11                             ` Eli Zaretskii
2006-10-19 13:28             ` Daniel Jacobowitz
2006-10-19 15:59               ` Andrew STUBBS
2006-10-18 19:22           ` Eli Zaretskii
2006-10-11 22:06   ` Mark Kettenis
2006-10-12 10:45     ` Andrew STUBBS

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=uac3rqzz6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.stubbs@st.com \
    --cc=gdb-patches@sourceware.org \
    /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