commit access

Richard Laager rlaager at
Sat Mar 29 21:20:46 EDT 2008

On Mon, 2007-11-05 at 20:46 +0100, Bjoern Voigt wrote:
> So I (and probably the other translators too) call "intltool-update XX" 
> (XX is the language code) directly. And intltool-update is both an 
> external script (e.g. /usr/bin/intltool-update) and a copy of this 
> script named pidgin-mtn/intltool-update. Normally 
> /usr/bin/intltool-update will be called, if the user types 
> "intltool-update XX". Hardcoding of "XGETTEXT_ARGS=--no-location" into 
> pidgin-mtn/intltool-update is not a good choice, because 1) it's 
> probably not called by the translator and 2) the translator sometimes 
> needs the location information during the translation.
> So I only see 2 choices:
>    1. We document the usage of "(XGETTEXT_ARGS=--no-location)
>       intltool-update XX) for the translators.

What ever became of this? I thought that we (or maybe it was just me)
had asked for translators to use XGETTEXT_ARGS=--no-location when
committing translations, but that's clearly not happening most of the
time. Is there some reason we want the location information committed?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the Devel mailing list