Re: making changes to Makefile.in.in to allow multiple domains

[Bruno Haible]

Yann Dirson wrote:
> However, there were already a couple of complaints that it is far less
> practical for translation teams and for the translation coodinator.
> With my modified system, a single team could easily ship updates for
> all of the 8 textdomains in a single mail, as they were named
> $domain.po.  Now that they are named $lang.po, all the 8 files sent by
> a single team basically all have the same name, which makes the
> translation maintainance more error-prone.

The Free Translation Project uses the convention $domain-$version.$lang.po
for all PO files transferred by mail. It is then the maintainer's
responsibility to store this file in the right directory as $lang.po.
This convention is not as error-prone as the one that you mention.

The maintainer must rename the PO files anyway, because of the version:
For the translators it is better to have the version in the filename,
whereas a maintainer doesn't want to have the version in the filename when
he distributes po/*.po files.

Bruno