Re: [gettext] Translations under a language's main dialect are not found if LANGUAGE contains only the language code

[Bob Proulx]

Gunnar Hjalmarsson wrote:
> Bruno Haible wrote:
> > Gunnar Hjalmarsson wrote:
> >> [ resending this with the gettext address instead of
> >> address@hidden Don't know if it matters, considering that the
> >> lists are archived together. ]
> > 
> > Sure it matters. bug-gnu-gettext, bug-sed, bug-gawk, bug-diff have different
> > subscribers, but the archive is shared.
> 
> To me it looks like the mailman list is shared as well, and that other
> addresses but address@hidden are aliases. If it's possible to
> subscribe to bug-gnu-gettext only, I'd appreciate a pointer to some
> resource that explains how.

I think that regardless of some of these being aliases to the same
mailing list that whatever is documented should be the preferred
address.  Right now some of those are aliases but that can change at
any time.  (I don't recall at the moment but an alias was converted to
a full mailing list just recently.)  It is harder to go wrong if you
follow the documented procedure and addresses.  And if it does go
wrong anyway then you can point to the documentation and blame it. :-)

bug-gnu-utils is a real mailing list.  But bug-sed, bug-gawk,
bug-diff, and bug-gnu-gettext are aliases to it.  You can't subscribe
to them individually.  These are project aliases installed on
fencepost.gnu.org.

The aliases sometimes have additional recipients such as bug-gawk and
bug-gnu-gettext that both go directly to their respective maintainers
in addition to the mailing list.  So one critical difference is for
the maintainers that are sometimes subscribed directly, and possibly
only, through the alias and not the generic, combined, multiple use
mailing list.  The alias might be the only way for the maintainer to
see the message.  Bruno gets a direct copy of bug-gnu-gettext messages
but not for bug-gnu-utils.  The same for Arnold who gets a direct copy
of bug-gawk.  This is the reason it is important to always follow the
preferred reporting address.

That is also why you will sometimes see replies from the maintainers
before the message to the mailing list has made it through
lists.gnu.org.  When lists.gnu.org is behind handling email then they
still get their copy and can look at the email and don't have to wait
for the mailing lists to catch up.

I hope that helps to clear things up.

Bob