Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: improved thread id reporting
Date: Tue, 07 Apr 2009 15:18:00 -0000	[thread overview]
Message-ID: <e394668d0904061637r49f93a32o163798227791edb9@mail.gmail.com> (raw)
In-Reply-To: <m31vs54fqm.fsf@fleche.redhat.com>

On Mon, Apr 6, 2009 at 2:46 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Doug> +      printf_filtered (_("[Switching from thread #%d, %s\n"),
> Doug> +                pid_to_thread_id (previous_inferior_ptid),
> Doug> +                target_pid_to_str (previous_inferior_ptid));
> Doug> +      printf_filtered (_("             to thread #%d, %s]\n"),
>
>>> This approach to lining things up is not i18n-friendly.
>
> Eli> Sorry, I'm probably too dense today: why not?  If you are thinking
> Eli> about the number of blanks, then the translated second message can
> Eli> change their amount as appropriate, no?
>
> Only if the translator knows to do that.

I realize this is digressing but y'all are too. :-)
I was thinking that the translation might just punt on the spacing, I
was more worried about some language that preferred to/from, but since
this was just an example I wasn't worried about such issues.


  reply	other threads:[~2009-04-06 23:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 19:06 Doug Evans
2009-04-04 19:07 ` Mark Kettenis
2009-04-04 20:40   ` Daniel Jacobowitz
2009-04-04 21:21     ` Eli Zaretskii
2009-04-04 22:17       ` Daniel Jacobowitz
2009-04-05  1:11         ` Doug Evans
2009-04-05  3:42         ` Eli Zaretskii
2009-04-05  3:48           ` Daniel Jacobowitz
2009-04-05  7:19           ` Paul Pluzhnikov
2009-04-05 18:50             ` Eli Zaretskii
2009-04-05 20:11               ` Paul Pluzhnikov
2009-04-05 20:36                 ` Eli Zaretskii
2009-04-04 22:35     ` Doug Evans
2009-04-06  2:58     ` Doug Evans
2009-04-06  3:33       ` Eli Zaretskii
2009-04-06 15:36         ` Mark Kettenis
2009-04-06 20:21           ` Eli Zaretskii
2009-04-06  7:39       ` Daniel Jacobowitz
2009-04-06 21:21         ` Eli Zaretskii
2009-05-08  5:43         ` Doug Evans
2009-04-06 20:20       ` Tom Tromey
2009-04-06 20:20         ` Eli Zaretskii
2009-04-06 22:15           ` Tom Tromey
2009-04-07 15:18             ` Doug Evans [this message]
2009-04-04 22:24   ` Doug Evans
2009-04-05  3:13     ` Daniel Jacobowitz
2009-04-05  9:16       ` Mark Kettenis
2009-04-05 18:23         ` Eli Zaretskii
2009-04-05 19:22       ` Doug Evans
2009-04-04 19:20 ` Thiago Jung Bauermann
2009-04-04 19:21   ` Eli Zaretskii

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=e394668d0904061637r49f93a32o163798227791edb9@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.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