bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Benno Schulenberg <coordinator@translationproject.org>
Cc: bug-gnulib@gnu.org, Akim Demaille <akim.demaille@gmail.com>
Subject: Re: gnulib's translation
Date: Sat, 01 Dec 2018 17:00:33 +0100	[thread overview]
Message-ID: <6927537.DgX8tGiBJN@omega> (raw)
In-Reply-To: <E0481821-DC0D-4549-9788-BB59D78E25A9@gmail.com>

[CCing the TP coordinator]

Hi Benno,

Akim has just moved some code from Bison to Gnulib. He writes:

> Also, I feel sorry for Bison's translators when submitting modules to gnulib: it's kind of throwing away their work; it would be great if there were a means to preserve these translations.  Maybe the translation project is able to fill the translations of one project based on that of another, I don't know.

What is the recommended procedure, to save translator work, when a number
of messages have been moved from one domain to another domain (both domains
are managed by the TP)?

Bruno



  parent reply	other threads:[~2018-12-01 16:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26  6:18 gnulib's translation Akim Demaille
2018-12-01 11:50 ` Akim Demaille
2018-12-01 15:57 ` Bruno Haible
2018-12-01 16:36   ` Akim Demaille
2018-12-01 16:41     ` Akim Demaille
2018-12-01 19:47     ` Bruno Haible
2018-12-02  6:04       ` Akim Demaille
2018-12-02 12:10         ` Bruno Haible
2018-12-02 14:38           ` Benno Schulenberg
2018-12-02 15:55             ` Paul Smith
2018-12-02 16:47               ` Bruno Haible
2018-12-02 16:46             ` Bruno Haible
2018-12-02 14:31       ` Benno Schulenberg
2018-12-06 18:11   ` Akim Demaille
2018-12-07  3:33     ` Bruno Haible
2019-01-12  7:28       ` Akim Demaille
2019-02-05 19:09         ` Akim Demaille
2018-12-01 16:00 ` Bruno Haible [this message]
2018-12-02 14:27   ` Benno Schulenberg

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=6927537.DgX8tGiBJN@omega \
    --to=bruno@clisp.org \
    --cc=akim.demaille@gmail.com \
    --cc=bug-gnulib@gnu.org \
    --cc=coordinator@translationproject.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).