From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Improving the translation process
Date: Fri, 07 Feb 2020 22:50:13 +0100 [thread overview]
Message-ID: <8736bm12zu.fsf@gnu.org> (raw)
In-Reply-To: <5C0BF556-0087-41D9-AFF1-A48F3762CC04@lepiller.eu> (Julien Lepiller's message of "Thu, 06 Feb 2020 12:01:51 -0500")
Hello!
Julien Lepiller <julien@lepiller.eu> skribis:
> This new process would allow for daily or weekly updates of
> translations, which fits better with our rolling-release model and
> will help translators of the manual do work on a regular basis instead
> of per-release. The interface is way more understandable for newcomers
> who will quickly understand how to contribute. The downside is, as
> always, more fragmentation in the l10n community esp. if we go for our
> own instance.
The first two arguments are very compelling to me.
The counter-argument, I don’t know; in practice, it seems that Guix
translators are mostly involved with Guix, no?
I don’t know Weblate but if it works for you translators and doesn’t
require us maintainers (well, me!) to open a JS-enabled browser and
click through, I’m all for it. :-)
BTW, in the meantime, would you feel like uploading a tarball to the TP
so we can give translators some time to start updating everything?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-02-07 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 17:01 Improving the translation process Julien Lepiller
2020-02-06 19:20 ` Julien Lepiller
2020-02-06 21:41 ` pelzflorian (Florian Pelz)
2020-02-07 13:00 ` Julien Lepiller
2020-02-07 13:46 ` pelzflorian (Florian Pelz)
2020-02-07 21:50 ` Ludovic Courtès [this message]
2020-02-09 23:55 ` zimoun
2020-02-10 0:03 ` Julien Lepiller
2020-02-11 14:23 ` Ludovic Courtès
2020-02-11 16:08 ` Julien Lepiller
2020-02-24 16:23 ` Ludovic Courtès
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=8736bm12zu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.