unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Translation Project Robot <robot@translationproject.org>
To: libc-alpha@sourceware.org
Subject: New template for 'libc' made available
Date: Tue, 11 Dec 2012 08:10:10 +0100	[thread overview]
Message-ID: <E1TiJyk-0003tY-0A@duik.vrijschrift.org> (raw)

Hello, gentle maintainer.

This is a message from the Translation Project robot.  (If you have
any questions, send them to <coordinator@translationproject.org>.)

A new POT file for textual domain 'libc' has been made available
to the language teams for translation.  It is archived as:

    http://translationproject.org/POT-files/libc-2.17-pre1.pot

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

Below is the URL which has been provided to the translators of your
package.  Please inform the translation coordinator, at the address
at the bottom, if this information is not current:

    ftp://alpha.gnu.org/gnu/glibc/glibc-2.17-tps.tar.gz

We can arrange things so that translated PO files are automatically e-mailed
to you when they arrive.  Ask at the address below if you want this.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coordinator@translationproject.org>



             reply	other threads:[~2012-12-11  7:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11  7:10 Translation Project Robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-03 10:38 New template for 'libc' made available Translation Project Robot
2023-07-18 14:07 Translation Project Robot
2023-01-25 10:19 Translation Project Robot
2022-07-31  9:09 Translation Project Robot
2022-01-30 15:39 Translation Project Robot
2021-07-29  8:00 Translation Project Robot
2020-07-23  7:17 Translation Project Robot
2020-01-10  9:00 Translation Project Robot
2019-07-24 18:14 Translation Project Robot
2019-01-16 16:40 Translation Project Robot
2018-07-27 18:54 Translation Project Robot
2018-01-10 19:12 Translation Project Robot
2017-07-25 19:05 Translation Project Robot
2017-01-11 13:46 Translation Project Robot
2017-01-11 13:41 Translation Project Robot
2015-07-31  7:18 Translation Project Robot
2015-08-02 20:20 ` Jochen Hein
2015-08-03 17:06   ` Joseph Myers
2015-08-03 18:50     ` Carlos O'Donell
2015-08-03 19:08       ` Paul Eggert
2015-08-03 20:34       ` Joseph Myers
2015-08-04 14:30         ` Carlos O'Donell
2015-01-22 19:22 Translation Project Robot
2014-08-21  7:39 Translation Project Robot
2014-01-08 12:37 Translation Project Robot
2013-07-26  8:04 Translation Project Robot
2012-06-30 16:24 Translation Project Robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1TiJyk-0003tY-0A@duik.vrijschrift.org \
    --to=robot@translationproject.org \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).