From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: tromey@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: start of i18n
Date: Sat, 22 Jun 2002 10:25:00 -0000 [thread overview]
Message-ID: <2427-Sat22Jun2002202250+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3D149CE7.4070405@cygnus.com> (message from Andrew Cagney on Sat, 22 Jun 2002 11:51:03 -0400)
> Date: Sat, 22 Jun 2002 11:51:03 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
> >
> > Speaking as a translator, freezing the strings before the release is a
> > good practice. It would be nice if GDB followed it.
>
> How much before? 1 week, 1 month, ...
A couple of weeks at least. It depends on the number of messages to
translate, but I expect GDB to have a lot of them.
> - branch gdb
> - week later, freeze strings
>
> that leaves ~4-6 weeks.
That might not be a good idea, since freezing strings only a week
after the branch is too early; chances are later changes will have to
modify the messages to some extent.
It's better to leave 2 weeks extra between the day you are confident
a release is ready and the actual release. Then just resync with the
Translation Project database before you tar the release.
> By ``string freeze'' does that mean no new strings or, for late breaking
> strings, not internationalizing them (omit the _(".."))?
Yes, it means that translatable strings will not be added or modified
after the string freze.
> Do the translators prefer to keep the trunk up-to-date or do they wait
> for the release cycle?
They wait for a new version of the catalog (po/gdb.pot) file to be
submitted to the Translation Project Robot. Then they update their
translations and submit them to the Robot.
> I've no idea what sort of process the translators follow or prefer here.
See
http://www.iro.umontreal.ca/contrib/po/HTML/
It's all there.
next prev parent reply other threads:[~2002-06-22 17:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 10:10 Tom Tromey
2002-06-21 10:22 ` Andrew Cagney
2002-06-21 10:49 ` Tom Tromey
2002-06-21 12:06 ` Andrew Cagney
2002-06-21 13:13 ` Tom Tromey
2002-06-22 2:47 ` Eli Zaretskii
2002-06-22 8:51 ` Andrew Cagney
2002-06-22 10:25 ` Eli Zaretskii [this message]
2002-06-26 20:15 ` Andrew Cagney
2002-06-21 10:46 ` Elena Zannoni
2002-06-21 10:50 ` Tom Tromey
2002-06-21 15:13 ` Andrew Cagney
2002-06-21 15:57 ` Tom Tromey
2002-06-21 16:13 ` Andrew Cagney
2002-06-21 16:45 ` Tom Tromey
2002-06-22 15:24 ` [patch] Update selftest.exp; Was: " Andrew Cagney
2002-06-22 18:13 ` 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=2427-Sat22Jun2002202250+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@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