Re: ALL_LINGUAS

[Keld Jørn Simonsen <keld dkuug dk>]

On Wed, Jan 22, 2003 at 04:37:56PM +0100, Carlos Perelló Marín wrote:
> El mié, 22-01-2003 a las 16:33, Keld Jørn Simonsen escribió:
> > On Wed, Jan 22, 2003 at 04:06:41PM +0100, Christian Rose wrote:
> > > ons 2003-01-22 klockan 15.46 skrev Tino Meinen:
> > > > Just curious,
> > > > When adding a new translation to a module in the po directory, 
> > > > 
> > > > whose responsibility is it to add the language to the ALL_LINGUAS list
> > > > in configure.in?
> > > 
> > > Usually the responsibility of the translator that added the po file.
> > > Pablo Saratxaga has been very nice in fixing missing language codes in
> > > the ALL_LINGUAS of many modules (thanks a lot!), though. But all
> > > translators should really make sure themselves that their own language
> > > code is present in ALL_LINGUAS.
> > > 
> > > So:
> > > ########################################################################
> > > When you add a new translation to a module and want the translation to
> > > be used, make sure you also add the language code of the translation to
> > > the ALL_LINGUAS line in the module's configure.in file. If you don't do
> > > that, the translation won't get picked up by the build system, and won't
> > > be used.
> > > ########################################################################
> > 
> > WHy is this necessary? Could the configure script not just look to see
> > which *.po files there are and use those? That woudl automate this
> > step.
> > 
> 
> Sometimes, a maintainer  should disable the use of some .po file because
> it's broken. If you do it automaticly you lose "features"

Hmm, if it is broken, then it probably would not compile, and then
the net result is the same, an unsupported language.

Probably, if what Pablo is saying is true, then it would be better
to have a EXCLUDE_LINGUAS to especially excude stuff, and then
automatically include all *.po files. Would save Pablo some work.

Kind regards
keld