You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by ma...@ukf.net on 2006/08/22 20:38:50 UTC
[l10n] Translation status for branches/1.4.x r21204
Translation status report for revision 21204 (branches/1.4.x/)
============================================================================
Status for 'de.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
53 untranslated
1425 translated, of which
74 fuzzy
----------------------------------------------------------------------------
Status for 'es.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
7 untranslated
1471 translated, of which
14 fuzzy
----------------------------------------------------------------------------
Status for 'fr.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
14 untranslated
1464 translated, of which
23 fuzzy
----------------------------------------------------------------------------
Status for 'it.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
9 untranslated
1469 translated, of which
24 fuzzy
----------------------------------------------------------------------------
Status for 'ja.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
0 untranslated
1478 translated, of which
0 fuzzy
----------------------------------------------------------------------------
Status for 'ko.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
9 untranslated
1469 translated, of which
52 fuzzy
----------------------------------------------------------------------------
Status for 'nb.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
1 untranslated
1477 translated, of which
2 fuzzy
----------------------------------------------------------------------------
Status for 'pl.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
49 untranslated
1429 translated, of which
127 fuzzy
----------------------------------------------------------------------------
Status for 'pt_BR.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
6 untranslated
1472 translated, of which
21 fuzzy
----------------------------------------------------------------------------
Status for 'sv.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
6 untranslated
1472 translated, of which
21 fuzzy
----------------------------------------------------------------------------
Status for 'zh_CN.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
62 untranslated
1416 translated, of which
319 fuzzy
----------------------------------------------------------------------------
Status for 'zh_TW.po': in repository
Passes GNU msgfmt --check-format
Statistics:
0 obsolete
6 untranslated
1472 translated, of which
21 fuzzy
----------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Update po files in the 1.4.x branch
Posted by Max Bowsher <ma...@ukf.net>.
Kobayashi Noritada wrote:
> Here is a gzipped patch to update po files in the 1.4.x branch. This
> is created by automatically running "make locale-gnu-po-update"
> (twice; please read the tailing part of this message.) and po-merge.
For any automated operations, it is better to send a list of commands to
run, rather than a patch. It is much easier for someone to review the
commands, than the copious diffs they generate.
I don't really understand about running the update twice - could you
clarify that?
Thanks,
Max.
[PATCH] Update po files in the 1.4.x branch (was: Re: [l10n]
Translation status for branches/1.4.x r21204)
Posted by Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp>.
Hi,
> We're going to need to do some po-merge.py-ing soon. The script
> itself seems straightforward enough: just go into a 1.4.x checkout and
> run something like "svn cat
> http://svn.collab.net/repos/svn/trunk/subversion/po/sv.po |
> po-merge.py sv.po".
Here is a gzipped patch to update po files in the 1.4.x branch. This
is created by automatically running "make locale-gnu-po-update"
(twice; please read the tailing part of this message.) and po-merge.
Since languages but for ja does not have translation for messages
updated recently (e.g. the help message for '--pre-1.4-compatible'),
this patch does not complete translation in the 1.4.x branch for any
languages. But, it improves situation like this:
Status for original po files (r21229):
Translation status report for revision 21229 (branches/1.4.x)
============================================================================
lang untrans fuzzy trans obs
de.po 32 12 1397 0
es.po 2 0 1469 89
fr.po 5 0 1465 0
it.po 0 0 1469 0
ja.po 0 0 1478 266
ko.po 0 32 1470 0
nb.po 0 0 1478 0
pl.po 28 69 1401 43
pt_BR.po 0 0 1473 0
sv.po 0 0 1473 0
zh_CN.po 0 213 1373 19
zh_TW.po 0 0 1473 59
Status for original po files against current source code (r21229 +
po-update):
Translation status report for revision 21229 (branches/1.4.x)
============================================================================
lang untrans fuzzy trans obs
de.po 53 74 1425 12
es.po 8 14 1470 96
fr.po 15 23 1463 10
it.po 10 24 1468 10
ja.po 0 0 1478 266
ko.po 10 52 1468 10
nb.po 2 2 1476 3
pl.po 49 127 1429 56
pt_BR.po 7 21 1471 10
sv.po 7 21 1471 10
zh_CN.po 62 319 1416 61
zh_TW.po 7 21 1471 69
Status for po files here against current source code (r21229 +
po-update + po-merge):
Translation status report for revision 21229 (branches/1.4.x)
============================================================================
lang untrans fuzzy trans obs
de.po 53 74 1425 12
es.po 7 1 1471 96
fr.po 1 1 1477 10
it.po 1 1 1477 10
ja.po 0 0 1478 266
ko.po 7 9 1471 10
nb.po 2 2 1476 3
pl.po 35 128 1443 56
pt_BR.po 1 1 1477 10
sv.po 7 20 1471 10
zh_CN.po 62 319 1416 61
zh_TW.po 7 20 1471 69
> Folks who've done this before: do I want to run and check in the
> result of "make locale-gnu-po-update" on trunk and/or 1.4.x before I
> do merges? Or will this confuse translators? (TRANSLATING says that
> I *can* run locale-gnu-po-update on branches, but I'm not sure if it's
> the right thing to do right now.)
I always check after running "make locale-gnu-po-update", since it
breaks order of obsolete messages. It does not break po files but
makes diff larger. I know running the command twice works well.
Thanks,
-nori
Re: [l10n] Translation status for branches/1.4.x r21204
Posted by David Glasser <gl...@mit.edu>.
We're going to need to do some po-merge.py-ing soon. The script
itself seems straightforward enough: just go into a 1.4.x checkout and
run something like "svn cat
http://svn.collab.net/repos/svn/trunk/subversion/po/sv.po |
po-merge.py sv.po".
Folks who've done this before: do I want to run and check in the
result of "make locale-gnu-po-update" on trunk and/or 1.4.x before I
do merges? Or will this confuse translators? (TRANSLATING says that
I *can* run locale-gnu-po-update on branches, but I'm not sure if it's
the right thing to do right now.)
--dave
--
David Glasser | glasser@mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Updated subversion/po/zh_CN.po for trunk and
branches/1.4.x (was: [l10n] Translation status for branches/1.4.x r21204)
Posted by Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp>.
Hi,
(Rock, sorry for my late reply to your message,
<c7...@mail.gmail.com> )
> > Note that a fair number of these are better on trunk (though the ones
> > in need of the most work, de and zh_CN, are not yet).
>
> Sorry for finishing it so late,
No, no, thank you for working quickly. :-)
> Yesterday I sent the nearly finised translation to some boards at
> a BBS here, and I got very little feedback, it seems very few people
> are interested in translation (indeed, it's not so interesting...).
I agree. I have had the same experience... Many users and
programmers does not get interested in translation itself.
But translators usually have their own community; they usually reviews
each other's translation. So, I think you can find one some time. :-)
> I will send the po files to svn-users mail list, but I'm afraid they
> can't be reviewed enough before 1.4.0 released, so I hope they can
> be committed to repos first and then wait somebody to maintain them.
> (If nobody stands out, I would like to do this job)
Great!! Thank you very much for posting a po file, Yubao.
Rock, I'd like you to review the po file. You seem to be used to
translation works, at least for Subversion. I believe you can help
Liu Yubao very well.
Yubao and Rock, I'd like you to contact to each other (maybe in the
Simplified Chinese) to brush up the translation. After that work,
please repost the po file here. It may take some days to brush up,
but the release time for 1.4.0 is at least one week later; you can
make new zh_CN.po in time.
Erik or David, could you please create commit access to the repository
for them?
> Note I have not reviewed all the old translated items, I think they
> need be reviewed again.
Yes, you are right. To correct mistakes and to make translations
consistent, you should do so. But it can be done after releasing the
1.4.0.
> BTW: Noritada, thank you again for your guide, I find Emacs with po mode
> is really wonderful:-)
One more suggestion. If you cannot understand the message itself, you
can type 's' to refer to the source code. It sometimes helps me.
# Of course, there are still many error messages I have no idea how to
# translate...
Best wishes,
-nori
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
[PATCH] Updated subversion/po/zh_CN.po for trunk and branches/1.4.x
(was: [l10n] Translation status for branches/1.4.x r21204)
Posted by Liu Yubao <yu...@gmail.com>.
David Glasser wrote:
> On 8/22/06, Max Bowsher <ma...@ukf.net> wrote:
>> Hmm, the previous format is rather long-winded. Here's a tabular form.
>>
>> Translation status report for revision 21204 (branches/1.4.x/)
>
> Note that a fair number of these are better on trunk (though the ones
> in need of the most work, de and zh_CN, are not yet).
>
> --dave
>
Sorry for finishing it so late, last weekend I prepared to start
translation, but I found I hadn't merged zh_CN.po with latest
subversion.pot and I couldn't connect to internet at home :-(
Yesterday I sent the nearly finised translation to some boards at
a BBS here, and I got very little feedback, it seems very few people
are interested in translation (indeed, it's not so interesting...).
I will send the po files to svn-users mail list, but I'm afraid they
can't be reviewed enough before 1.4.0 released, so I hope they can
be committed to repos first and then wait somebody to maintain them.
(If nobody stands out, I would like to do this job)
Note I have not reviewed all the old translated items, I think they
need be reviewed again.
I have run "make locale", it's ok.
Any suggestions or comments are welcomed.
BTW: Noritada, thank you again for your guide, I find Emacs with po mode
is really wonderful:-)
Best regards,
Liu Yubao
Re: [l10n] Translation status for branches/1.4.x r21204
Posted by David Glasser <gl...@mit.edu>.
On 8/22/06, Max Bowsher <ma...@ukf.net> wrote:
> Hmm, the previous format is rather long-winded. Here's a tabular form.
>
> Translation status report for revision 21204 (branches/1.4.x/)
Note that a fair number of these are better on trunk (though the ones
in need of the most work, de and zh_CN, are not yet).
--dave
--
David Glasser | glasser@mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [l10n] Translation status for branches/1.4.x r21204
Posted by David Glasser <gl...@mit.edu>.
On 8/22/06, Max Bowsher <ma...@ukf.net> wrote:
> Hmm, the previous format is rather long-winded. Here's a tabular form.
Committed a change in r21216 which makes it output more of a tabular form.
It would be convenient to move the report-generation changes over to
1.4.x to help us check the status on the branch, so I nominated these
changes in STATUS. tools/ changes just require one more +0 or +1
(concept) anyway, so hopefully this can be taken care of quickly. I
certainly don't think that rc5 should block on this change, but
backporting it should help the 1.4.x release process.
--dave
--
David Glasser | glasser@mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
[l10n] Translation status monitoring and updates
Posted by Max Bowsher <ma...@ukf.net>.
Kobayashi Noritada wrote:
> Fabien COELHO wrote:
>> IMVHO, if such nice statistics could be send say once a week, to the dev
>> list, or to the "po" committers, or to some web page, or rss... maybe with
>> some warnings about approaching deadlines, that would help;-)
>
> Erik (aka dionisos) sent such reports both for trunk and for the
> release branch two or three times a week in the 1.1.x/1.2.x ages.
> IMHO, those reports are necessary and helpful for the release branch
> (not for the trunk) before the first patch release (1.x.0) gets out
> (and also a week before other patch releases gets out, if possible).
>
> The deadlines may be only known by reading messages with a subject
> line containing words such as "release" or "roll" on this list.
> Time to releases always changes. ;-)
If someone would like to hack together a script that outputs a HTML
and/or RSS file, I will set it up under http://www.red-bean.com/svnproject/
If we decide on where and how frequently automated emails should be
sent, I will set up appropriate cronjobs.
Max.
Re: [l10n] Translation status for branches/1.4.x r21204
Posted by Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp>.
Hi,
> > ja 0 0
ja always keeps up with code, since I'm always checking locally
whether new messages get available after any code changes both in the
trunk and in the 1.4.x release branch. :-)
Fabien COELHO wrote:
> IMVHO, if such nice statistics could be send say once a week, to the dev
> list, or to the "po" committers, or to some web page, or rss... maybe with
> some warnings about approaching deadlines, that would help;-)
Erik (aka dionisos) sent such reports both for trunk and for the
release branch two or three times a week in the 1.1.x/1.2.x ages.
IMHO, those reports are necessary and helpful for the release branch
(not for the trunk) before the first patch release (1.x.0) gets out
(and also a week before other patch releases gets out, if possible).
The deadlines may be only known by reading messages with a subject
line containing words such as "release" or "roll" on this list.
Time to releases always changes. ;-)
Regards,
-nori
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [l10n] Translation status for branches/1.4.x r21204
Posted by Fabien COELHO <fa...@coelho.net>.
> Hmm, the previous format is rather long-winded. Here's a tabular form.
> Translation status report for revision 21204 (branches/1.4.x/)
>
> lang untrans fuzzy
> ---------------------
> zh_CN 62 319
> de 53 74
> pl 19 127
> fr 12 23
I'll see what I can do about the French translation.
> ko 9 52
> it 9 24
> es 7 14
> pt_BR 6 21
> sv 6 21
> zh_TW 6 21
> nb 1 2
> ja 0 0
IMVHO, if such nice statistics could be send say once a week, to the dev
list, or to the "po" committers, or to some web page, or rss... maybe with
some warnings about approaching deadlines, that would help;-)
--
Fabien.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [l10n] Translation status for branches/1.4.x r21204
Posted by Max Bowsher <ma...@ukf.net>.
Hmm, the previous format is rather long-winded. Here's a tabular form.
Translation status report for revision 21204 (branches/1.4.x/)
lang untrans fuzzy
---------------------
zh_CN 62 319
de 53 74
pl 19 127
fr 12 23
ko 9 52
it 9 24
es 7 14
pt_BR 6 21
sv 6 21
zh_TW 6 21
nb 1 2
ja 0 0
Max.