Re: how to harvest translatable strings from generated files?

[Paul Pogonyshev]

Bruno Haible wrote:
> Paul Pogonyshev wrote:
> > > You can either create the dummy C file in the source directory, and
> > > distribute it with your package. The same way as you handle the output
> > > from bison or flex.
> >
> > This is not an option here, as some of the C files depend on `configure'
> > results.  Even if those with translatable strings currently don't,
> > splitting over it looks ugly.
>
> How can this work? You've got a problem here: If the POT file that would
> be generated, say, on FreeBSD differs from the POT file on, say, Linux,
> which one would be sent to the translators?
>   - Sometimes one, sometimes the other? The translators will say "thank
> you" when they realize that some messages have been dropped and then
> reintroduced again.
>   - Always the Linux one? Then the FreeBSD user will never have a fully
>     localized application.
>   - Always the FreeBSD one? Then the Linux user ...
>
> Really, the POT file needs to be platform independent.

No, strings don't depend on the `configure' output, but some other things
do.  And the strings with these ``other things'' happen to be in the same
kind of files, which are processed with the same custom tool.

Paul