fetchmail-devel

[fetchmail-devel] translations for message catalogs, info and inquiry

[Matthias A. <ma...@dt...>]

Hi,

I have recently joined the de...@li... translation team and negotiated a
cold but welcome takeover of the de.po file.

While we're getting 6.2.6 ready for shipping, we need to tell the
translation project some bits of information:

- who the maintainer is and where we want updated .po files sent by the
  translation project (the .po files contain the translations)
  and where distribution tarballs can be downloaded. The current record
  that they have is:

|  <domain>fetchmail
|  <mailto>es...@th...
|  <keep>6.0.0<keep>6.1.3<keep>6.2.0<keep>6.2.3<keep>6.2.4
|  <autosend>
|  <url>http://www.catb.org/~esr/fetchmail/fetchmail-6.2.5.tar.gz
|  <ext>cs<ext>pt_BR

  <ext> means that ESR is getting the cs and pt_BR translations directly
  from the maintainers, not via the translation project, so we should
  probably Cc: these maintainers when sending the .pot file and making
  them aware of the new location of the site and maintainer and
  everything. See also: 
  http://www.iro.umontreal.ca/translation/HTML/maintainers.html

  Do we want to have this mailing list listed as the "mailto" and
  the place where the .po files be sent? We'll need to allow the bot's
  address to the list, apparently it's either gnutra@ or translation@
  iro.umontreal.ca.

- the current 6.2.6 .pot file
  (which contains the untranslated original messages)

  NOTICE #1: this is actually the URL for a .pot file that we're telling
  them.

  NOTICE #2: we cannot send multiple .pot files with one and the same
  version number, we'll need distinct version numbers if we plan to
  revise the code. We can use 6.2.5.99.1 for a release candidate and
  then perhaps bump to 6.2.6 if we haven't made message changes later.

  I'll handle this when we're sure about how 6.2.6 will finally look like.

-- 
Matthias Andree

Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)

Re: [fetchmail-devel] translations for message catalogs, info and inquiry

[Rob F. <rf...@fu...>]

Matthias Andree wrote:
>   <ext> means that ESR is getting the cs and pt_BR translations directly
>   from the maintainers, not via the translation project, so we should
>   probably Cc: these maintainers when sending the .pot file and making
>   them aware of the new location of the site and maintainer and
>   everything.

Sounds like we should start compiling a list of everyone to email when we do 
the changeover announcement.

>   Do we want to have this mailing list listed as the "mailto" and
>   the place where the .po files be sent?

Probably should, unless anyone can think of a better place.

>   We'll need to allow the bot's 
>   address to the list, apparently it's either gnutra@ or translation@
>   iro.umontreal.ca.

Worst case we add it when Mailman holds it back.


Thanks for handling the translation issues!

-- 
==============================| "A slice of life isn't the whole cake
 Rob Funk <rf...@fu...> | One tooth will never make a full grin"
 http://www.funknet.net/rfunk |    -- Chris Mars, "Stuck in Rewind"

Re: [fetchmail-devel] translations for message catalogs, info and inquiry

[Matthias A. <mat...@gm...>]

Rob Funk <rf...@fu...> wrote on 2004-09-02:

> Sounds like we should start compiling a list of everyone to email when we do 
> the changeover announcement.

I have requested that the translation registry be changed, as can be
seen from the Cc: to this list that should appear in a few minutes.

>>   Do we want to have this mailing list listed as the "mailto" and
>>   the place where the .po files be sent?
>
> Probably should, unless anyone can think of a better place.

No better suggestions have been posted, so I've asked for this list's
address.

>>   We'll need to allow the bot's 
>>   address to the list, apparently it's either gnutra@ or translation@
>>   iro.umontreal.ca.
>
> Worst case we add it when Mailman holds it back.

Yup. Do you want to add me as moderator for fetchmail-devel?

> Thanks for handling the translation issues!

OK. I'll release a snapshot under the version of 6.2.5.991 to an
inofficial FTP site and have it translated so we can see to updating the
.po files.

We should probably get a 6.2.6 or 6.3.0 release out the door quick
(i. e. in March 2005) to provide the public with the fixes we have
merged, and so that fetchmail sees a new release within 18 months after
the previous one. If you do not have the time to work on fetchmail,
we'll have to find more developers and perhaps reassign maintainership
again to help, now that Graham has had to quit.

-- 
Matthias Andree