From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: i18n mark-up
Date: Sun, 08 Aug 2004 15:16:00 -0000 [thread overview]
Message-ID: <411643D6.6030607@gnu.org> (raw)
In-Reply-To: <1190-Sun08Aug2004065623+0300-eliz@gnu.org>
>>> Date: Sat, 07 Aug 2004 16:12:09 -0400
>>> From: Andrew Cagney <cagney@gnu.org>
>>>
>>> Does anyone have any suggestions on how we should approach the task of
>>> marking up GDB's source for i18n?
>
>
> Any reason why it shouldn't be done as for any other program? That
> is, use gettext tools to extract messages to a catalogue, then wrap
> each message string in the sources with the _() macro call, and add
> the rest of the infrastructure for the translated catalogues?
and all have been implemented as you suggest.
Well, almost. We've still got the tinyiest of tasks of marking up GDB's
source with those _() macros :-)
Andrew
next prev parent reply other threads:[~2004-08-08 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 20:12 Andrew Cagney
2004-08-08 3:59 ` Eli Zaretskii
2004-08-08 15:16 ` Andrew Cagney [this message]
2004-08-08 19:22 ` Eli Zaretskii
2004-08-11 17:54 ` Andrew Cagney
2004-08-12 4:00 ` 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=411643D6.6030607@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).