From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Translating news on weblate?
Date: Sun, 07 Aug 2022 12:56:35 +0200 [thread overview]
Message-ID: <877d3knwyk.fsf@pelzflorian.de> (raw)
In-Reply-To: <20220721222734.0f0ac881@sybil.lepiller.eu> (Julien Lepiller's message of "Thu, 21 Jul 2022 22:27:34 +0200")
Hi Julien; sorry for the late answer.
Julien Lepiller <julien@lepiller.eu> writes:
> I was thinking we could have our news file translated at weblate, which
> would help having more people translate it. Attached is a script that[…]
Translating etc/news.scm via Weblate adds delay but reaches more
translators. Now delay is not so important when reading old news from
--list-generations or when one hasn’t upgraded in a while, but I would
prefer if those who make news, continue to request translations on some
mailing list (I forgot the name of the list alias; where is it?). Even
though I was too slow to react to such mail in the past, I think I can
improve.
Also, Weblate has lazy commits
<https://docs.weblate.org/en/latest/admin/continuous.html#lazy-commit>,
i.e., it only commits new changes to your (Julien’s) repository after a
while, which adds slightly more delay when it comes to news, unless the
uploader or a news download script logs in and uses the Web API’s File
Download button. Or maybe the hypothetical Fedora Weblate component for
Guix news can be configured to push changes to your repo right away.
Thank you Julien for your maintenance of translations! There’s not much
to say about your nice script.
Regards,
Florian
next prev parent reply other threads:[~2022-08-07 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 20:27 Translating news on weblate? Julien Lepiller
2022-07-22 10:20 ` Taiju HIGASHI
2022-07-28 14:09 ` Thiago Jung Bauermann
2022-08-03 18:00 ` Ludovic Courtès
2022-08-07 10:56 ` pelzflorian (Florian Pelz) [this message]
2022-08-07 11:55 ` Maxime Devos
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d3knwyk.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).