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

Checking format strings in .po files (fwd)

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-06-23 23:31:42 CEST

[It might work if I use the correct list address...]

---------- Forwarded message ----------
Date: Wed, 23 Jun 2004 23:17:06 +0200 (CEST)
From: Peter N. Lundblad <peter@famlundblad.se>
To: Erik Huelsmann <e.huelsmann@gmx.net>
Cc: devel@subversion.tigris.org
Subject: Checking format strings in .po files

[Moving this discussion to the dev list]

On Wed, 23 Jun 2004, Erik Huelsmann wrote:

> > On Wed, 23 Jun 2004, Greg Stein wrote:
> >
> > > For translations... heck yah. That's an even lower part than partial
> > > commit access to the raw code.
> > >
> > Hmmm... Remember that a translation is part of the code. A bad translation
> > can introduce crashes due to formatting strings. But only for that
> > language. That was why I wanted to add --check-format to the msgfmt
> > command line some week ago.
>
> I think we can't do that in the Makefile, but I could include this check in
> my cronjob (which I will commit when it proves alright).
>
But we could add the -c option in the Makefile if we add
Last-Translator: Subversion Developers <dev@subversion.tigris.org>
to every .po file. (In fact my msgfmt only checks that the header is
there, so we could possibly leave it empty, but that's ugly.)

I'd like to have the check in the regular build so we make sure we don't
release with a translation which crashes svn.

If no one objects, I can do this in all .po files and change the
Makefile.in. Anyone knows if -c is available in other msgfmt programs that
we support?

//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 23 23:28:11 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.