From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] More NEWS for 6.3
Date: Wed, 03 Nov 2004 18:05:00 -0000 [thread overview]
Message-ID: <01c4c1cf$Blat.v2.2.2$044d91c0@zahav.net.il> (raw)
In-Reply-To: <4188EE65.5050700@gnu.org> (message from Andrew Cagney on Wed, 03 Nov 2004 09:42:45 -0500)
> Date: Wed, 03 Nov 2004 09:42:45 -0500
> From: Andrew Cagney <cagney@gnu.org>
> Cc: gdb-patches@sources.redhat.com
>
> > Fine with me, although I suggest to lose the i18n part, since without
> > a message catalog, we cannot say we support it.
>
> (well I do have a "strine" catalogue if you're interested :-)
> I've checked it in (6.3 and mainline).
Why did you say "strine"? By ``a catalog'' I meant the gdb.pot file,
which is in English, not in any specific language (yes, I know what
"strine" is).
Anyway, it's not enough to have a catalog, nor a translation for a
specific language. We need to register the "gdb" domain with the
Translation Project and then submit gdb.pot to the TP robot, so that
translators could work on producing the XX.po files. We should also
wait for a while after gdb.pot becomes available from the TP web
pages, to give translators time to translate, and finally we should
download the XX.po files and include them with the release tarball.
Then, and only then, we could say in good faith that GDB supports
i18n.
In case you didn't know, the details of this are spelled out here:
http://www.iro.umontreal.ca/translation/HTML/maintainers.html
prev parent reply other threads:[~2004-11-03 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 16:04 Andrew Cagney
2004-11-01 21:26 ` Eli Zaretskii
2004-11-03 14:42 ` Andrew Cagney
2004-11-03 18:05 ` Eli Zaretskii [this message]
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='01c4c1cf$Blat.v2.2.2$044d91c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@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