From: Translation Project Robot <robot@translationproject.org>
To: binutils@sources.redhat.com
Subject: New Dutch PO file for 'opcodes' (version 2.16.93)
Date: Wed, 11 Jul 2007 20:37:00 -0000 [thread overview]
Message-ID: <E1I8im7-0006mx-IY@neoduik.vrijschrift.org> (raw)
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'opcodes' has been submitted
by the Dutch team of translators. The file is available at:
http://translationproject.org/latest/opcodes/nl.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/opcodes/
Please consider including all of these in your next release, whether
official or a pretest.
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.
The following HTML page has been updated:
http://translationproject.org/domain/opcodes.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coordinator@translationproject.org>
next reply other threads:[~2007-07-11 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 20:37 Translation Project Robot [this message]
2007-07-11 22:57 Translation Project Robot
2007-07-12 21:52 Translation Project Robot
2007-07-16 12:11 ` Nick Clifton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1I8im7-0006mx-IY@neoduik.vrijschrift.org \
--to=robot@translationproject.org \
--cc=binutils@sources.redhat.com \
/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).