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

Re: Adapting build system for subversion.pot

From: Tobias Ringstrom <tobias_at_ringstrom.mine.nu>
Date: 2004-04-26 14:46:06 CEST

Erik Huelsmann wrote:

> Hi Tobias,
> To answer your question about adding pot generation targets to the build
> system:
> I was unable to decide between adding the following to Makefile.in and let
> someone else handle win32, or try to write a platform-independent python
> script.

We need consistent pot generation now, so I think it's fine to have a
simple solution for unix. If there is interest to do this in Windows
later, there can either be a specific solution for Windows, or a new
platform independent solution can be created.

> This will generate the right pot from the Makefile:
> locale-pot:
> find $abs_srcdir/subversion \
> -name bindings -prune -or \
> -name tests -prune -or \
> -name "*.c" -print -or \
> -name "svn_error_codes.h -print | \
> xgettext -k_ -kN_ \
> -o $abs_srcdir/subversion/po/subversion.pot
> Comments?

I think you missed a "-" option to xgettext to make it read filenames
from stdin.

It would be nice to have a "-name .svn -prune -or" as well to make it a
little faster.

It's bad to use absolute paths because those paths will propagate to the
po files which means that source browsing of the po files will only work
on the machine that created the pot file. It should work to cd to
$abs_srcdir/subversion before running find.

It's probably a good idea to use -F with xgettext or add a sort in the
pipe to get stable results on different machines. It is of course
better to use -F with msgmerge, but it's nice to use it with xgettext as
well to get stable results even if you forget it or don't know about it.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 26 14:46:47 2004

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.