Re: [Translation-i18n] The reason for make dist updating po files

[Bruno Haible <bruno clisp org>]

Kenneth Rohde Christiansen wrote:
> > wonder why you haven't asked for version numbers in po/Makefile.in.in.
> 
> Yeah, I should probably have done that. Can you add that?

OK, starting from gettext 0.12.2, Makefile.in.in will carry a version number.

> With intltool it is possible to define the format in POTFILES.in, like:
> 
> [type: gettext/xml] data/start-here.xml
> src/main.c
> src/test.c
> [type: gettext/ini] data/mimefile.keys

Aha, that's what allows you to distinguish various kinds of XML...

> > * intltool-update:
> >   Do you think some of this is general enough that it belongs into GNU gettext?
> >   If so, which parts? Btw, is intltool-update a tool for translators or for
> >   developers?
> 
> Some of it yes. I would really like an option like --maintain for
> gettext.

Hmm, indeed "intltool-update --maintain" is helpful for the maintainer.
(But it shouldn't recommend to add src/po-gram-gen.c to POTFILES.in when
src/po-gram-gen.y is already listed.)

Something like this could become part of automake's "make dist" target,
but I don't see yet how to write this in such a way that it is customizable
enough (depending on the project's structure and file types).

Bruno