Re: po / pot file integration: documentation

[Bruno Haible]

Hi Ralf,

Thanks for the review of the spec.

> > +This example uses wildcards.  ...
> > address@hidden
> > +locale_POTS = po/maude.pot
> > +po_maude_pot_SOURCES = src/**/*.c
> > +po_maude_pot_SOURCES_EXCLUDE = src/version.c
> > address@hidden smallexample
> 
> Can we omit this for now?  It can still be added at a later point in
> time, maybe together with its implementation.

OK, fine with me. So we'll make the _SOURCES list an explicit variable,
and not document _SOURCES_EXCLUDE for now.

> > +po_maude_pot_MSGID_BUGS_ADDRESS = bug-maude@@yoyodyne.com
> 
> There was an example domain for email addresses, but it wasn't
> example.com IIRC.  Using some arbitrary other one is not nice

It's not an arbitrary one. <http://en.wikipedia.org/wiki/Yoyodyne> says:
   "The Internet domain name yoyodyne.com was allocated by internet
    software designer TGV Inc. as a "fake" domain name for use in DNS
    configuration examples."
I chose it on purpose, because there is little risk that it collides with
a real company's address.

> > +Alternatively, you can also have the translation downloaded from a
> > +translation project when the package is built.  ...
> 
> Can't we have the cake and eat it too?  As in: ship translations but at
> configure time also try to download newer ones?  That would avoid both
> of these downsides, no?

Yes, very good point. I'll add that to the spec.

> With some of the semantics, I don't yet see how the implementation would
> work

Most of the features are already implemented in gettext autoconf macros
and Makefile.in.in rules. You can look there any time you don't understand
how it's meant to be implemented.


Thank for the texinfo and spelling related remarks; I'll fix them.

> > Feel free to put it on a git branch.
> 
> You can do it yourself, when we've hashed out all questions.

Thanks, I'll do it, with some fixes, in a couple of days.

Bruno