gtranslator.keys.in.in (was Re: [ Pozilla #7 ] gtranslator R 0.36)

[Christian Rose <menthos menthos com>]

Fatih Demir wrote:
> > You should probably change the name of
> > "data/mime/gtranslator.keys.in.in" to "data/mime/gtranslator.keys.in",
> > and also change the reference in po/POTFILES.in accordingly.
> > That will make that file be processed correctly by xml-i18n-tools and
> > the strings in that file turn up in the pot (which I think should be the
> > case).
> 
> This is not possible as gtranslator.keys.in.in is the base for
>  gtranslator.keys.in and created by configure.

Hmm, why should this file be created by configure? Isn't
gtranslator.keys.in what's used by configure to create gtranslator.keys
?


> And then xml-i18n-tools operate on the file -- it has got to be like it's
> now.

As it is now, xml-i18n-update won't recognize the gtranslator.keys.in.in
file, and those messages won't, as a result of that, end up in the pot
and therefore not in the translations. The only way I could make them
end up in the pot was by renaming the mime keys file to
gtranslator.keys.in in my copy of the source.

I'm cc:ing this to a xml-i18n-tools developer who probably knows the
answer to this.


Christian