Hi,
> Author: maxb
> Date: Wed Aug 23 11:57:34 2006
> New Revision: 21233
>
> Modified:
> trunk/subversion/po/de.po
> trunk/subversion/po/es.po
> trunk/subversion/po/fr.po
> trunk/subversion/po/it.po
> trunk/subversion/po/ja.po
> trunk/subversion/po/ko.po
> trunk/subversion/po/nb.po
> trunk/subversion/po/pl.po
> trunk/subversion/po/pt_BR.po
> trunk/subversion/po/sv.po
> trunk/subversion/po/zh_CN.po
> trunk/subversion/po/zh_TW.po
>
> Log:
> Execute po-update.sh on trunk.
I'd like to revert r21233, update of po files for all languages,
since it is hard to merge that change to local currently-working po
files. At least for zh_CN.po, updating works is going on locally (and
the worker, Liu Yubao, does not have a commit access now). IMHO,
running po-update.sh for po files all together in the trunk is
harmful (I know it works for the release branch).
Also, please make sure to run msgmerge (or "make
locale-gnu-po-update", or po-update.sh) twice, not once. As I wrote
in <20060824.033121.41641653.nori1@dolphin.c.u-tokyo.ac.jp>,
msgmerge breaks order of obsolete messages; it does not break po files
itself, but makes diff too larger. I don't know why, but running it
twice works well. We should describe about this to the TRANSLATING,
or should implement po-update to run msgmerge twice.
(I do not want to cut off obsolete messages, since they are sometimes
necessary for backporting messages to the branches.)
Regards,
-nori
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 23 22:44:58 2006