public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Translation Project Robot <robot@translationproject.org>
To: gcc-patches@gcc.gnu.org
Subject: New Swedish PO file for 'gcc' (version 12.2.0)
Date: Fri, 26 Aug 2022 22:52:24 +0200	[thread overview]
Message-ID: <E1oRgJU-0001vn-GH@duik.vrijschrift.org> (raw)

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators.  The file is available at:

    https://translationproject.org/latest/gcc/sv.po

(This file, 'gcc-12.2.0.sv.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    https://translationproject.org/latest/gcc/

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:

    https://translationproject.org/domain/gcc.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>


             reply	other threads:[~2022-08-26 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 20:52 Translation Project Robot [this message]
2022-10-02  9:22 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

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

  git send-email \
    --in-reply-to=E1oRgJU-0001vn-GH@duik.vrijschrift.org \
    --to=robot@translationproject.org \
    --cc=gcc-patches@gcc.gnu.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).