Re: Qt4, gettext and autopoint

[Leopold Palomo-Avellaneda]

A Dijous 26 Març 2009, Christophe Mutricy va escriure:
> Hello,
>
> Le Wed 25 Mar 09 à 19:48 +0100, Leopold Palomo Avellaneda a écrit :
> > A Dimecres 25 Març 2009, Christophe Mutricy va escriure:
> > > Hello,
> > >
> > > In VLC, we use mainly C and auto*. So it just works with gettext and
> > > the Makefile.in.in installed by autopoint.
> > >
> > > Now, it gets more tricky with the Qt4 interface. No problem with the
> > > strings in the C++ files. But the strings in the .ui files cause
> > > problems.
> > > These .ui files are xml files and are translated in C headers files by
> > > uic which take care of transforming the xml-escaped strings in proper C
> > > strings.
> > > Running msgfmt on the .h files works OK but as they are generated files
> > > we don't keep them in Git and they are in builddir rather than srcdir.
> > >
> > > So first question: Is there a way to have files in
> > > ${top_builddir}/foo/bar in POTFILES.in
> > >
> > > Another option would be to run sed (or another program) on the .ui
> > > before parsing them with msgfmt. I can't find a way to do that with the
> > > default Makefile.in.in installed by autopoint. Have I mised something?
> >
> > We pass the .h files to xgettext (not msgfmt?)
>
> Hmm i meant xgettext. I shouldn't write mail too late at night.

I think that you are not the only one that do this. ;-)

> > So, I think that it's better to pass the .h files to xgettext and not the
> > .ui,
>
> I agree
>
> > OTOH, I'm almost sure that you can put a list of files that are generated
> > in the potfiles.in. We do it with cmake, so I think that autotools have
> > some similar method.
>
> That where it causes problem for me because it will look for the
> generated files in srcdir and not builddir and a lot of us really like
> to have srcdir!=builddir

Well,

probably the autotools guru could help you. I don't know if there's some list 
of autotools. You can always think to migrate to cmake ....

OTOH Qt 4.5 support gettext files. I don't know how. I should say that I don't 
like Qtlinguist because I think that it doesn't work so good ad gettext and 
is a bit complicated in the translator view.

Regards,

Leo