From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Translating the web site
Date: Mon, 05 Oct 2020 14:17:59 +0200 [thread overview]
Message-ID: <87ft6s27ew.fsf@gnu.org> (raw)
In-Reply-To: <19944324-1441-4209-A94C-0C03B4434609@lepiller.eu> (Julien Lepiller's message of "Thu, 24 Sep 2020 07:21:22 -0400")
Hi Julien,
Julien Lepiller <julien@lepiller.eu> skribis:
> Le 24 septembre 2020 03:25:56 GMT-04:00, "Ludovic Courtès" <ludovic.courtes@inria.fr> a écrit :
>>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.
>
> No, weblate works with a git repository: it clones a repo and presents translation files to the users. Wher a file it translated, it commits it locally and remotely.
>
>>
>>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.
>
> So, we really need a git repository. I guess it could be hosted on, say, git.guix.gnu.org :)
Can we agree on the next steps so that this issue doesn’t stall?
My understanding is that we need:
1. A public Git repo with all the POT files. We can file a support
request at Savannah to get that under the ‘guix’ project.
2. Registration at fedora-project.org.
3. Publicity so we actually get translations.
Is that correct?
I can help with #1, that’s my contribution. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-10-05 12:18 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
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 [this message]
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
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=87ft6s27ew.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).