From: Julien Lepiller <julien@lepiller.eu>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel <guix-devel@gnu.org>,
"operator.name" <operator.name@protonmail.com>
Subject: Re: Cookbook translations
Date: Tue, 28 Apr 2020 14:23:32 -0400 [thread overview]
Message-ID: <EE9CD61D-59B9-46CE-A608-0E787B930EEE@lepiller.eu> (raw)
In-Reply-To: <20200428194633.509a93ce@alma-ubu>
Le 28 avril 2020 13:46:33 GMT-04:00, "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de> a écrit :
>Hi Florian,
>
>On Tue, 28 Apr 2020 01:42:31 +0200
>"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
>
>> On Tue, Apr 28, 2020 at 01:24:30AM +0200, Björn Höfling wrote:
>> > I wondered: do you know how the cookbook translations are
>> > organized?
>
>[..]
>
>> The cookbook is not available at the TP because no POT file is
>shipped
>> in Guix’ tarball. Julien suggested moving the translation from the
>TP
>> infrastructure to a Weblate setup (which I agree Guix should try and
>> experiment with), so instead of waiting for inclusion of the cookbook
>> at the TP I just commited the German translation directly to Guix
>> master without going through the Translation Project. (It is
>> important that the version at the TP is the most current version, but
>> since there is no cookbook at the TP, it does not matter currently.)
>>
>> Regards,
>> Florian
>
>I see.
>
>Do you want to use the hosted version of Weblate or are there plans to
>host it within Guix?
>
>I just wondered because Weblate uses Node/yarn packages:
>
>https://github.com/WeblateOrg/weblate/blob/master/scripts/yarn/package.json
>
>Would that be OK for just hosting it as a service or do we need the
>npm/yrn-importer first? :-)
>
>Björn
The translation project is already hosted outside the guix project, so I don't see any issue if we're not able to package it just yet.
hosted.weblate.org has some tracking in place (a matomo instance hosted by the weblate author). I wouldn't like to expose our users to it. Fedora has a weblate instance open to any free software project with no tracking, so I was suggesting using it instead.
next prev parent reply other threads:[~2020-04-28 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 23:24 Cookbook translations Björn Höfling
2020-04-27 23:42 ` pelzflorian (Florian Pelz)
2020-04-28 17:46 ` Björn Höfling
2020-04-28 18:23 ` Julien Lepiller [this message]
2020-04-29 19:52 ` Björn Höfling
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=EE9CD61D-59B9-46CE-A608-0E787B930EEE@lepiller.eu \
--to=julien@lepiller.eu \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=operator.name@protonmail.com \
--cc=pelzflorian@pelzflorian.de \
/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).