這是轉錄自 gnome-i18n mailing list 的信, 希望對有興趣的人有點幫助
Message: 4
Date: Fri, 11 Aug 2000 11:31:22 +0000 (GMT)
From: root <root(a)pc96.ma.rhbnc.ac.uk>
To: zhaoway <zw(a)zhaoway.com>
Cc: gnome-i18n(a)gnome.org
Subject: Re: howto get pot files
On Fri, 11 Aug 2000, zhaoway wrote:
> please how can i get pot files in a
> easy way? i want to help the zh_CN
> pot translation.
Afaik, currently you need to download (CVS) the whole source tree of
the application you need to translate and create an updated .po to check
the messages.
For example, for gnome-core
1. setenv CVSROOT ':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'
2. cvs login (press enter for password)
3a. cvs -z3 checkout gnome-core (if it's the first time you grab
gnome-core)
[SEVERAL MBs downloaded]
3b. cvs -z3 update -Pd gnome-core (if you have already an older
version
of gnome-core)
[SEVERAL MBs downloaded]
4. cd gnome-core/po
5. ./update.sh (this creates an updated
gnome-core.pot)
6. ./update.sh zh_CN (this creates an updated zh_CN.po,
you use this for translations)
On (6), if there is no already a zh_CN.po file, it does not work. You
need
to copy gnome-core.pot to zh_CN.po, set the fields of the header and
translate.
Suppose that there was a cron application that every day went to each
gnome-PACKAGE/po/ and updated at least the gnome-PACKAGE.pot.
Downloading
just gnome-PACKAGE.pot and the previous translation of zh_CN.po, you
could
do the updates with just those two files.
You would then do:
(suppose you already logged on CVS)
% cvs -z3 checkout gnome-core/po/gnome-core.pot
% cvs -z3 checkout gnome-core/po/zh_CN.po
% cd gnome-core/po
% msgmerge --strict --verbose -o `date "+%d%h%y-"`zh_CN.po zh_CN.po
gnome-core.pot
In this case, you update the 11Aug2000-zh_CN.po file and submit it.
To be extra cool with the "version" field of the .po file you just
translated, you would also need to do:
% cvs -z3 checkout gnome-core/configure.in
In this file, it says the exact new version of the gnome package. (It is
not updated automatically from the update procedure).
Alternatively, the cron daemon could run the "update.sh" script for all
languages and all packages every day so that you would just need to
download one file per package, namely zh_CN.po. Even better, since the
file is then available, one could link it to
http://www.gnome.org/i18n/release/status.shtml, so that with just the
browser you could download, update and submit.
All these are nice with two gotchas:
a. You need a lot of experience to be able to translate the messages
without having access to the program/source code. Brings down quality?
b. Automatic updates could possibly make translations a moving target.
The msgmerge program could destroy some .po files. This needs some
testing
to verify.
HIH,
simos
--__--__--
_______________________________________________
gnome-i18n mailing list
gnome-i18n(a)gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
--
XLinux Inc.
System Engineer
南方四劍客 mailto:michael@xlinux.com
[Patrick D'Cruze]
> [...] as Pofeng mentions in his email, there may be political consequences
> of using Taiwanese resources/mailing list to develop ZH support for
> GNU/Linux.
One problem is that the Translation Project publishes one team address
per team. Whatever the address we use, the other party might be unhappy.
If technical stunts are avoidable, I would prefer this. But if avoiding
technical stunts create endless problems or irritation, better swallow
the snake and do whatever need to be done.
However, I hope to think that political problems are not so big that we
need technical stunts around them. After all, we are here to collaborate
to a planetary project, not to fight each other...
> Hmm. I'm not sure what the best solution is.
Patrick, if you are available to discuss the matter with Chinese people,
I will be more than happy to not play the intermediary between the Chinese
team and Linux International, as this only slows down discussions. I will
comply, of course, to the solution you will all come up.
Keep happy, all!
--
François Pinard http://www.iro.umontreal.ca/~pinard
[Pofeng Lee]
> I am going to resign from the coordinator ( the team leader ). And Mr
> Shyue will take this job. [...] What else we should do ?
OK, I made the changes in the TP registry. Please check:
http://www.iro.umontreal.ca/contrib/po/HTML/team-zh.html
and tell me if I goofed in any way.
> But I think we can set up a mailing list gateway between zh(a)li.org &
> zh-l10n(a)li.org.tw to avoid political problem :-) .
Patrick, would you have `zh(a)li.org' forward into `zh-l10n(a)li.org.tw'?
Doing so, messages sent to `zh(a)li.org' will be seen by `zh-l10n(a)li.org.tw'
members. But if you also manage to send `zh-l10n(a)li.org.tw' into
`zh(a)li.org', I presume loops might occur unless special dispositions are
taken to avoid such problems. Could current `zh(a)li.org' members subscribe
into `zh-l10n(a)li.org.tw'?
> There is an interesting relationship between Mainland China & Taiwan.
> I am afraid that if we change the address, some people would get upset
> about that. Before that, I would stay on zh(a)li.org & zh-l10n(a)linux.org.tw.
Things are not fully set up, currently in the Translation Project, for
having many official addresses for a single team, but if it just cannot
be avoided, I could dive into the robot code and try to manage something.
Thing would be much simpler if we had a single official address for the team.
May we try using the new email address for a while, and see how translators
react? I presume everybody will understand that no offence is intended?
Is that workable, and acceptable?
--
François Pinard http://www.iro.umontreal.ca/~pinard
--
Welcome to the zh mailing list!
Please save this message for future reference. Thank you.
If you ever want to remove yourself from this mailing list,
you can send mail to <Majordomo(a)li.org> with the following
command in the body of your email message:
unsubscribe zh
or from another account, besides to-zh-l10n(a)linux.org.tw:
unsubscribe zh to-zh-l10n(a)linux.org.tw
If you ever need to get in contact with the owner of the list,
(if you have trouble unsubscribing, or have questions about the
list itself) send email to <owner-zh(a)li.org> .
This is the general rule for most mailing lists when you need
to contact a human.
Here's the general information for the list you've subscribed to,
in case you don't already have it:
Hello! Welcome to the Chinese translators team. We need people, like
you, who are ready to *work* in collaboration with us in translating
messages into Chinese for GNU programs, and maybe other Linux programs
as well. We collectively seek high quality translations for Chinese,
using a common terminological basis which we'll develop as we go. You
offer us a good knowledge of Chinese, an open mind, and teamwork skills.
We are happy to have you with us!
But if, while just wandering around, you subscribed by mistake, and do not
feel like being an active member of our team, please unsubscribe yourself
by sending a message to <zh-request(a)li.org>, with the word:
unsubscribe
in the body of the message. We're aiming to keep the lists focused
on active development and workers - and besides our list server is
already pretty over-loaded. I hope you understand our policy.
If you decide to stay with us, please introduce yourself to the
other members of the team by writing to <zh(a)li.org>, explaining why
and how you are interested in helping, telling your strong and weak
points, so everybody will feel more ready to talk with you how
the work should be split, and shared.