From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Translating the web site
Date: Thu, 24 Sep 2020 09:25:56 +0200 [thread overview]
Message-ID: <875z83bpq3.fsf@inria.fr> (raw)
In-Reply-To: <5CF9034A-6518-4E56-9F78-C19A4AC0CF46@lepiller.eu> (Julien Lepiller's message of "Wed, 23 Sep 2020 08:50:46 -0400")
Hi,
Julien Lepiller <julien@lepiller.eu> skribis:
> As soon as we can host the translation files on a separate project on
> savannah, we can get it running at translate.fedora-project.org
Sounds good. Do we need to host POT files on our side? I naively
though Weblate would host them.
A Savannah project would be a sledgehammer; what about having a
sub-directory at guix.gnu.org with all the POT files? All we’d need to
do is add a couple of nginx ‘location’ blocks to the config in
maintenance.git.
> (it's a bit weird, but I think it's better than hosted.weblate.org
> which uses some google stuff. If we prefer hosted, there's ~1 month
> delay for them to consider an application).
Who is “them” in this last sentence?
> Eventually it could be nice to have our own instance, but dividing the
> translator community even further might not be a very good idea.
Yeah.
> To get the project, we need to clarify the license on the translation files, as we discussed before. How should we proceed on that?
There was a question about copyright holders for translations; to me
it’s clearly individual translators, and translations that indicate
otherwise are probably the result of misconfiguration in ‘Makevars’
and/or copy/paste.
The PO files at <https://translationproject.org/domain/guix.html> and
<https://translationproject.org/domain/guix-packages.html> state:
This file is distributed under the same license as the guix package.
which is perfect.
Those at <https://translationproject.org/domain/guix-manual.html> have
the same statement, but it should rather be the same license as the
manual (GFDL). Perhaps a ‘Makevars’ issue too? Since there are a
handful of translators involved, we can probably just contact them and
change that sentence.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2020-09-24 7:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:42 Translating the web site Ludovic Courtès
2020-09-23 12:50 ` Julien Lepiller
2020-09-23 14:13 ` pelzflorian (Florian Pelz)
2020-09-24 7:25 ` Ludovic Courtès [this message]
2020-09-24 8:50 ` etc/news copyright (was Re: Translating the web site) pelzflorian (Florian Pelz)
2020-09-24 9:13 ` Ludovic Courtès
2020-09-24 9:18 ` Konrad Hinsen
2020-09-24 11:14 ` Julien Lepiller
2020-09-24 17:45 ` Marius Bakke
2020-09-24 11:21 ` Translating the web site Julien Lepiller
2020-09-24 12:02 ` zimoun
2020-09-24 13:23 ` Julien Lepiller
2020-09-24 14:14 ` zimoun
2020-09-24 13:18 ` Ludovic Courtès
2020-09-24 13:31 ` Julien Lepiller
2020-09-24 14:34 ` pelzflorian (Florian Pelz)
2020-09-24 14:44 ` zimoun
2020-09-24 15:30 ` Julien Lepiller
2020-10-05 12:15 ` Ludovic Courtès
2020-10-05 14:06 ` Julien Lepiller
2020-10-12 10:01 ` Ludovic Courtès
2020-10-05 12:17 ` Ludovic Courtès
2020-10-05 13:17 ` Julien Lepiller
2020-10-12 12:29 ` Ludovic Courtès
2020-10-12 13:49 ` Julien Lepiller
2020-10-13 13:09 ` Ludovic Courtès
2020-10-07 21:54 ` Joshua Branson
2020-10-12 9:58 ` Ludovic Courtès
2020-10-11 13:57 ` Manual license (was Re: Translating the web site) Miguel Ángel Arruga Vivas
2020-10-11 15:39 ` Julien Lepiller
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=875z83bpq3.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--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.