From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Translating news on weblate?
Date: Wed, 03 Aug 2022 20:00:45 +0200 [thread overview]
Message-ID: <87sfmdqkaa.fsf@gnu.org> (raw)
In-Reply-To: <20220721222734.0f0ac881@sybil.lepiller.eu> (Julien Lepiller's message of "Thu, 21 Jul 2022 22:27:34 +0200")
Hi Julien,
Julien Lepiller <julien@lepiller.eu> skribis:
> 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
> is able to generate a pot file from the news.scm file and a translated
> news.scm file from the existing news.scm and a directory that contains
> the po files and a LINGUAS file.
I agree with what others said: it’s a great idea!
> The goal is to regularly fetch the news.scm file, generate a new pot
> that would automatically be updated on weblate. Translators can do
> their work, and the result is regularly merged back (after being
> checked that it doesn't break) in our repo.
>
> The script tries to reformat the news in a standard way and to merge
> existing copyright lines with the authorship lines in the po files. It
> is also able to generate the initial po files that I would give
> weblate, so translators don't have to redo translations that have
> already been done.
I was wondering whether we could just use xgettext to get a .pot file,
but maybe it doesn’t matter.
Given that these are news, I guess we’ll have to merge translations more
frequently than usual.
> (define <channel-news-entry> (@@ (guix channels) <channel-news-entry>))
Nitpick: You can (and should :-)) avoid this one.
Anyway, thumbs up, let’s do that!
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-08-03 18:01 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 [this message]
2022-08-07 10:56 ` pelzflorian (Florian Pelz)
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=87sfmdqkaa.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 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).