po/{zh_CN,ja}.po haven't been updated by r19334

Tao Wang dancefire at gmail.com
Tue Jul 13 07:50:30 EDT 2010


I checked the way we generating .pot and updating the po files. Currently we
use several hand-make programs to do the job. However, I think we'd better
use intltool-update, which is more standard.

"intltool-update -m" can check POTFILES.in and detect new/missing .c,
.glade, .schemas.in, which contains translatable strings. It cannot detect
.scm file. So, for the *.scm file, we should manually added them to
POTFILES.in. We currently use 'make-gnucash-potfiles' to generate the
POTFILES.in automatically. We have POTFILES.in in the repository anyway, so
I think it's better we manually add file names to POTFILES.in, it's not that
dynamic which should be generated each time for build. We can use
"intltool-update -m" as a verification tool for checking the newly added
file or deleted file.

"intltool-update -p" can extract the translatable strings from .c, .glade, .
schemas.in, .scm, .desktop.in, etc.. So, for the new strings, it can easily
merged them to .pot file. So, we may not need intl-scm/* to parse all *.scm
file and generate a fake guile-string.h for generating .pot file.
"intltool-update -p" is able to extract strings from *.scm file.

I can work on it, if there is anything I should know, just tell me.

On Tue, Jul 13, 2010 at 6:55 PM, Tao Wang <dancefire at gmail.com> wrote:

> 2010/7/13 Christian Stimming <stimming at tuhh.de>
>> Am Tuesday 13 July 2010 schrieb Tao Wang:
>> > Did you forget update the pot file in TP? I just updated zh_CN.po using
>> > latest pot from trunk. However, TP robot said the .pot file is not fully
>> > matched, and merged the my latest zh_CN.po with the old pot.
>> >
>> > ---------------------------------------------------------------------->
>> > --- gnucash-2.3.14.zh_CN.po~
>> > +++ gnucash-2.3.14.zh_CN.po
>> > @@ -13,7 +13,7 @@
>> >  msgstr ""
>> >  "Project-Id-Version: gnucash 2.3.14\n"
>> >  "Report-Msgid-Bugs-To: \n"
>> > -"POT-Creation-Date: 2010-07-13 12:42+1000\n"
>> > +"POT-Creation-Date: 2010-06-05 15:40-0400\n"
>> *sigh* Now you finally found out by yourself the single big problem of the
>> Translation Project: As the upstream coordinators, we cannot easily update
>> the
>> pot template which is stored at the TP. Instead, it will be updated only
>> if we
>> release a new version of the gnucash package. As a workaround, the TP
>> suggests
>> we can "release" a pre-version which is only sent to the TP and nowhere
>> else
>> (like a gnucash-2.3.15-pre1), but I never liked that solution because
>> those
>> "pre-"packages always get confused with the "real" ones. In the meantime,
>> my
>> conclusion is that it is not possible to update the pot at the TP at will,
>> only at release time.
>> Regards,
>> Christian
> That's bad. But, anyway, I can wait for the next release.
> l10n.gnome.org can track several branches, including the 'master' branch.
> Non of them have to be static. I think l10n.gnome.org can handle ".c,
> .scm, .glade, schemas.in" files, I found a project gnome-games use them
> and seems works fine at l10n.gnome.org:
> http://l10n.gnome.org/module/gnome-games/
> I also like decentralized Git for development. We can use both
> git.gnome.org and github.com. We can use github.com for decentralized
> development, and push back to git.gnome.org, as an official repository, at
> any stage. Git is quite free to use in either centralized or decentralized
> way, which is hard to do in subversion. And it's damn fast.
> --
> Regards
> Tao Wang


Tao Wang

More information about the gnucash-devel mailing list