[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Switch to Translation project for Subversion?

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Fri, 25 Apr 2014 16:37:00 +0100 (BST)

Mattias Engdegård wrote:
> On to practical matters: The source distribution, including pre-releases, should
> contain a generated .pot file for translators to base their work upon. (In
> theory, whoever makes the release could build the .pot manually and send it to
> the translators, but for Subversion, they are likely to need the entire .tar
> file.)
> I suppose it means that po-update.sh should be invoked from dist.sh. Would
> something like this be right (untested):
> +# Generate the .pot file, for use by translators.
> +echo "Running po-update.sh in sandbox, to create subversion.pot..."
> +(cd "$DISTPATH" && tools/po/po-update.sh pot) || exit 1
> (By the way, I see that nobody has run po-update in trunk for some time; it
> (rightly) complains about format strings.)

We should run the po-update script regularly, to find such problems early. It's quick, so I don't see why we should not run it as part of a default build, if the relevant dependencies are found on the system.

Then the distribution script won't need to do anything special.

Does that make sense?

(I looked in to the warnings currently produced. I'll email separately about fixing them.)

- Julian
Received on 2014-04-25 17:37:35 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.