From: Eli Zaretskii <eliz@is.elta.co.il>
To: Tom Tromey <tromey@redhat.com>
Cc: Gdb List <gdb@sources.redhat.com>
Subject: Re: Questions about gdb and gettext
Date: Mon, 24 Jun 2002 03:32:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020624132918.18662C-100000@is> (raw)
In-Reply-To: <87bsa1pvtv.fsf@fleche.redhat.com>
On 23 Jun 2002, Tom Tromey wrote:
> I personally have a preference for marking everything. I think it is
> easier to maintain, since the rule is easier to explain.
I agree.
> In the case of things like this, my current plan is to store the
> string in the command structure untranslated, and then translate when
> printing.
Agreed.
next prev parent reply other threads:[~2002-06-24 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-23 13:33 Tom Tromey
2002-06-23 14:33 ` Andrew Cagney
2002-06-23 21:52 ` Tom Tromey
2002-06-24 9:10 ` Andrew Cagney
2002-06-24 15:12 ` Tom Tromey
2002-06-24 3:32 ` Eli Zaretskii [this message]
2002-06-24 5:18 ` Richard Earnshaw
2002-06-24 11:17 ` 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=Pine.SUN.3.91.1020624132918.18662C-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--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