From: Andrew Cagney <cagney@gnu.org>
To: gdb@sources.redhat.com
Subject: GDB 6.4 and translations
Date: Wed, 03 Nov 2004 22:02:00 -0000 [thread overview]
Message-ID: <41895560.4030801@gnu.org> (raw)
Just so everyone is on the same page with this challenge.
GDB 6.3 is going to include a .pot file:
$ bunzip2 < gdb-6.2.90.tar.bz2 | tar tf - | grep gdb.pot
gdb-6.2.90/gdb/po/gdb.pot
(it's generated as part of the release process) but won't include any
corresponding translation.
Going on to 6.4, we'll need to quickly and efficiently:
- mark up a sizeable portion of the text
- ship the .pot file off for translation
(actually I've been asked to point at a download area - hence .50 and
snapshots/ directory changes) (I've not yet pushed a gdb.pot file
because it is effectively empty)
- wait for the translations
- integrate requested text changes and prototype text
and then iterate a bit. There are two time consuming tasks here:
- mark up text
- translate
For the second of those - translate - the translation project
[understandably] asks that they be allowed a significant amount of time
(months not weeks) for their work. Because of this, we'll need to
complete the bulk of the mark-up (create .pot files) very early in the
6.4 release cycle as otherwize we'll find ourselves either squeezing the
translation group's schedule, or having to let the translations slip out
to 6.4.1,.2,....
enjoy,
Andrew
next reply other threads:[~2004-11-03 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 22:02 Andrew Cagney [this message]
2004-11-04 4:39 ` Eli Zaretskii
2004-11-04 0:27 Paul Schlie
2004-11-04 4:52 ` Eli Zaretskii
2004-11-04 5:52 ` Paul Schlie
2004-11-04 8:11 ` Fabian Cenedese
2004-11-04 15:22 ` Daniel Jacobowitz
2004-11-04 16:21 ` Paul Schlie
2004-11-04 21:35 ` Eli Zaretskii
2004-11-04 15:34 ` Andrew Cagney
2004-11-04 16:55 ` Paul Schlie
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=41895560.4030801@gnu.org \
--to=cagney@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