Translating the web site

Translating the web site

[Ludovic Courtès]

Hello!

Thanks to Florian the web site is now internationalized… but it’s not
being translated for lack of a framework to do so.  (Specifically, the
Translation Project refused to host the web site’s POT files after we
told them we may eventually switch to Weblate, which I can understand.)

Julien, what do you think are the odds of getting a Weblate instance up
and running soonish?  (Also depending on your availability.)

What do you think can be done in the meantime?  Should we use the
infrastructure of another project (GNOME?), or should we simply do it in
an ad-hoc fashion by publishing the POT files at guix.gnu.org?
Thoughts?

Thanks,
Ludo’.

Re: Translating the web site

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

Hi,

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 (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). Eventually it could be nice to have our own instance, but dividing the translator community even further might not be a very good idea.

To get the project, we need to clarify the license on the translation files, as we discussed before. How should we proceed on that?

Le 23 septembre 2020 07:42:34 GMT-04:00, "Ludovic Courtès" <ludovic.courtes@inria.fr> a écrit :
>Hello!
>
>Thanks to Florian the web site is now internationalized… but it’s not
>being translated for lack of a framework to do so.  (Specifically, the
>Translation Project refused to host the web site’s POT files after we
>told them we may eventually switch to Weblate, which I can understand.)
>
>Julien, what do you think are the odds of getting a Weblate instance up
>and running soonish?  (Also depending on your availability.)
>
>What do you think can be done in the meantime?  Should we use the
>infrastructure of another project (GNOME?), or should we simply do it
>in
>an ad-hoc fashion by publishing the POT files at guix.gnu.org?
>Thoughts?
>
>Thanks,
>Ludo’.

[-- Attachment #2: Type: text/html, Size: 1662 bytes --]

Re: Translating the web site

[pelzflorian (Florian Pelz)]

Thank you for the heads-up.

On Wed, Sep 23, 2020 at 08:50:46AM -0400, Julien Lepiller wrote:
> Eventually it could be nice to have our own instance, but dividing
> the translator community even further might not be a very good idea.

Hmm it would seem nice if the Translation Project website would point
translators also to projects that do not use their infrastructure.
Have they disagreed on hyperlinking to weblate?

Regards,
Florian

Re: Translating the web site

[Ludovic Courtès]

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’.

etc/news copyright (was Re: Translating the web site)

[pelzflorian (Florian Pelz)]

[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]

On Thu, Sep 24, 2020 at 09:25:56AM +0200, Ludovic Courtès wrote:
> Julien Lepiller <julien@lepiller.eu> skribis:
> > 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’.

I’m fine with any licensing changes you see fit.

I guess we should add proper copyright notices to etc/news.scm too?

Sorry for not starting its translations with a proper copyright, but I
wasn’t sure because of etc/news.scm’s license:

“;; Copying and distribution of this file, with or without modification, are
;; permitted in any medium without royalty provided the copyright notice and
;; this notice are preserved.”

I attach a patch adding copyright notices, but I guess the authors
should agree.  I put them in Cc.

Regards,
Florian

[-- Attachment #2: 0001-news-Update-copyright.patch --]
[-- Type: text/plain, Size: 1235 bytes --]

From c84d333eea4ed5a654214d5cfa3186237c57bd69 Mon Sep 17 00:00:00 2001
From: Florian Pelz <pelzflorian@pelzflorian.de>
Date: Thu, 24 Sep 2020 10:37:51 +0200
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: [PATCH] news: Update copyright.

* etc/news.scm: Add missing copyright headers.
---
 etc/news.scm | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/etc/news.scm b/etc/news.scm
index 1ef238ca2d..86c1555fc7 100644
--- a/etc/news.scm
+++ b/etc/news.scm
@@ -2,8 +2,13 @@
 ;;
 ;; Copyright © 2019, 2020 Ludovic Courtès <ludo@gnu.org>
 ;; Copyright © 2019, 2020 Tobias Geerinckx-Rice <me@tobias.gr>
+;; Copyright © 2019, 2020 Konrad Hinsen <konrad.hinsen@fastmail.net>
+;; Copyright © 2019 Miguel <rosen644835@gmail.com>
+;; Copyright © 2019, 2020 Julien Lepiller <julien@lepiller.eu>
+;; Copyright © 2019, 2020 Florian Pelz <pelzflorian@pelzflorian.de>
 ;; Copyright © 2020 Mathieu Othacehe <m.othacehe@gmail.com>
 ;; Copyright © 2020 Jan (janneke) Nieuwenhuizen <janneke@gnu.org>
+;; Copyright © 2020 Marius Bakke <mbakke@fastmail.com>
 ;; Copyright © 2020 Maxim Cournoyer <maxim.cournoyer@gmail.com>
 ;;
 ;; Copying and distribution of this file, with or without modification, are
-- 
2.28.0

Re: etc/news copyright (was Re: Translating the web site)

[Ludovic Courtès]

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> I guess we should add proper copyright notices to etc/news.scm too?
>
> Sorry for not starting its translations with a proper copyright, but I
> wasn’t sure because of etc/news.scm’s license:
>
> “;; Copying and distribution of this file, with or without modification, are
> ;; permitted in any medium without royalty provided the copyright notice and
> ;; this notice are preserved.”

Yes, it’s the kind of all-permissive license found on gnu.org web pages
and recommended for short documents (info "(maintain) License Notices
for Other Files").

> I attach a patch adding copyright notices, but I guess the authors
> should agree.  I put them in Cc.

If the authors agree, fine with me!

Ludo’.

Re: etc/news copyright (was Re: Translating the web site)

[Konrad Hinsen]

Ludovic Courtès <ludovic.courtes@inria.fr> writes:

>> I attach a patch adding copyright notices, but I guess the authors
>> should agree.  I put them in Cc.
>
> If the authors agree, fine with me!

Since I am in CC, I must be one of the authors, though I don't really
remember what I could have contributed. Anyway, this is fine with me as
well!

Konrad.

Re: etc/news copyright (was Re: Translating the web site)

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

OK for me too!

Le 24 septembre 2020 05:18:30 GMT-04:00, Konrad Hinsen <konrad.hinsen@fastmail.net> a écrit :
>Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>
>>> I attach a patch adding copyright notices, but I guess the authors
>>> should agree.  I put them in Cc.
>>
>> If the authors agree, fine with me!
>
>Since I am in CC, I must be one of the authors, though I don't really
>remember what I could have contributed. Anyway, this is fine with me as
>well!
>
>Konrad.

[-- Attachment #2: Type: text/html, Size: 1015 bytes --]

Re: etc/news copyright (was Re: Translating the web site)

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 134 bytes --]

Julien Lepiller <julien@lepiller.eu> writes:

> OK for me too!

Ditto for me (I think I mainly copy-pasted another news item anyway).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Translating the web site

[Julien Lepiller]

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 :)

>
>> (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?  

hosted.weblate.org's admins. They try to make a bit of money from their project, so normally their service is paid, but they accept free software projects for free, but the application can take time.

>
>> 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?

I agree, the robot should have taken care of making sure the list of authors is maintained in the po files, so we have a complete list from that.

>
>Ludo’.

Re: Translating the web site

[zimoun]

Hi Julien,

On Thu, 24 Sep 2020 at 13:26, Julien Lepiller <julien@lepiller.eu> wrote:

> >> 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

Maybe I am doing wrong but <translate.fedora-project.org> seems down
or unreachable?

Cheers,
simon

Re: Translating the web site

[Julien Lepiller]

Le 24 septembre 2020 08:02:14 GMT-04:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi Julien,
>
>On Thu, 24 Sep 2020 at 13:26, Julien Lepiller <julien@lepiller.eu>
>wrote:
>
>> >> 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
>
>Maybe I am doing wrong but <translate.fedora-project.org> seems down
>or unreachable?

Sorry, it's translate.fedoraproject.org

>
>Cheers,
>simon

Re: Translating the web site

[zimoun]

On Thu, 24 Sep 2020 at 15:23, Julien Lepiller <julien@lepiller.eu> wrote:

> Sorry, it's translate.fedoraproject.org

Cool!
Well, managing the website translation with Weblate could be a
real-world example to test if Weblate helps in the translation
process.

All the best,
simon

Re: Translating the web site

[Ludovic Courtès]

Hi,

Julien Lepiller <julien@lepiller.eu> skribis:

>>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.

OK.

>>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 :)

Right, or, even easier: a sub-repository on Savannah under ‘guix’.
Would you like to file a support request on the Savannah web interface
so they create a new repo (just like we did for Cuirass, Guix Data
Service, etc.)?

>>> (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?  
>
> hosted.weblate.org's admins. They try to make a bit of money from their project, so normally their service is paid, but they accept free software projects for free, but the application can take time.

OK but like you said we probably don’t want to use hosted.weblate.org if
they use tracking services.

So let’s focus on Fedora’s instance.  (GNOME would be be a bit “closer”
to us, so to speak, but I don’t know if they run an instance nor if
they’d accept us.)

>>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?
>
> I agree, the robot should have taken care of making sure the list of authors is maintained in the po files, so we have a complete list from that.

OK, so Someone™ should email them to change the sentence to something
like “[…] under the same license as the Guix manual.”

Thanks,
Ludo’.

Re: Translating the web site

[Julien Lepiller]

Le 24 septembre 2020 09:18:52 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hi,
>
>Julien Lepiller <julien@lepiller.eu> skribis:
>
>>>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.
>
>OK.
>
>>>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 :)
>
>Right, or, even easier: a sub-repository on Savannah under ‘guix’.
>Would you like to file a support request on the Savannah web interface
>so they create a new repo (just like we did for Cuirass, Guix Data
>Service, etc.)?

We can't restrict commit access to one repo in a project with savannah. Are you OK with giving commit access to an external tool? It would be configured to push to that separate repo, but basically you're giving commit access to all of our repos (maintenance and guix itself) to fedora people :)

>
>>>> (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?  
>>
>> hosted.weblate.org's admins. They try to make a bit of money from
>their project, so normally their service is paid, but they accept free
>software projects for free, but the application can take time.
>
>OK but like you said we probably don’t want to use hosted.weblate.org
>if
>they use tracking services.
>
>So let’s focus on Fedora’s instance.  (GNOME would be be a bit “closer”
>to us, so to speak, but I don’t know if they run an instance nor if
>they’d accept us.)
>
>>>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?
>>
>> I agree, the robot should have taken care of making sure the list of
>authors is maintained in the po files, so we have a complete list from
>that.
>
>OK, so Someone™ should email them to change the sentence to something
>like “[…] under the same license as the Guix manual.”

I'll try to contact everyone today, but some of these emails might end up in a spam folder, because my server is so small. Can you also send something to the translators alias?

>
>Thanks,
>Ludo’.

Re: Translating the web site

[pelzflorian (Florian Pelz)]

On Thu, Sep 24, 2020 at 09:31:19AM -0400, Julien Lepiller wrote:
> I'll try to contact everyone today, but some of these emails might
> end up in a spam folder, because my server is so small. Can you also
> send something to the translators alias?

So aside from Julien and me that’s,
(from the French PO file) Simon Tournier,
(from the German PO file) Mario Blättermann, Jonathan Brielmaier,
(from the Russian PO file) znavko, Pavlo Marianov, Adam,
(for Spanish) Miguel, (for Chinese) Meiyo Peng, and, I
wonder, have Ali Reza Hayati and Amin Bandali been working on the
manual already; are they listed as part of the guix-i18n@gnu.org?
They had asked how they could help with translating on
<https://lists.gnu.org/archive/html/guix-devel/2020-08/msg00007.html>.

Regards,
Florian

Re: Translating the web site

[zimoun]

On Thu, 24 Sep 2020 at 16:37, pelzflorian (Florian Pelz)
<pelzflorian@pelzflorian.de> wrote:
>
> On Thu, Sep 24, 2020 at 09:31:19AM -0400, Julien Lepiller wrote:
> > I'll try to contact everyone today, but some of these emails might
> > end up in a spam folder, because my server is so small. Can you also
> > send something to the translators alias?
>
> So aside from Julien and me that’s,
> (from the French PO file) Simon Tournier,

All fine with me.

Thanks for working this.
simon

Re: Translating the web site

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

I've sent them all an email. Let's see what they say.

We still have the issue of the initial copyright line in the packages and guix translation. Some are to ludo, and it's easy to change. Some are to the FSF, and I'm not suse how we can change that. Should we ask them to allow the change? The rest is correctly attributed to the guix authors, but with different years.

Le 24 septembre 2020 10:34:24 GMT-04:00, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> a écrit :
>On Thu, Sep 24, 2020 at 09:31:19AM -0400, Julien Lepiller wrote:
>> I'll try to contact everyone today, but some of these emails might
>> end up in a spam folder, because my server is so small. Can you also
>> send something to the translators alias?
>
>So aside from Julien and me that’s,
>(from the French PO file) Simon Tournier,
>(from the German PO file) Mario Blättermann, Jonathan Brielmaier,
>(from the Russian PO file) znavko, Pavlo Marianov, Adam,
>(for Spanish) Miguel, (for Chinese) Meiyo Peng, and, I
>wonder, have Ali Reza Hayati and Amin Bandali been working on the
>manual already; are they listed as part of the guix-i18n@gnu.org?
>They had asked how they could help with translating on
><https://lists.gnu.org/archive/html/guix-devel/2020-08/msg00007.html>.
>
>Regards,
>Florian

[-- Attachment #2: Type: text/html, Size: 1788 bytes --]

Re: Translating the web site

[Ludovic Courtès]

Hi Julien,

Julien Lepiller <julien@lepiller.eu> skribis:

> I've sent them all an email. Let's see what they say.

I think we’re done, no?

Thanks,
Ludo’.

Re: Translating the web site

[Julien Lepiller]

Le 5 octobre 2020 08:15:26 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hi Julien,
>
>Julien Lepiller <julien@lepiller.eu> skribis:
>
>> I've sent them all an email. Let's see what they say.
>
>I think we’re done, no?

Unless I missed them, I still haven't got an answer from Mario Blättermann and Znavko.

I'm a bit worried that my messages ended up being filtered, as my mail server is so small. Can you try sending them something?

>
>Thanks,
>Ludo’.

Re: Translating the web site

[Ludovic Courtès]

Hi,

Julien Lepiller <julien@lepiller.eu> skribis:

> Le 5 octobre 2020 08:15:26 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>>Hi Julien,
>>
>>Julien Lepiller <julien@lepiller.eu> skribis:
>>
>>> I've sent them all an email. Let's see what they say.
>>
>>I think we’re done, no?
>
> Unless I missed them, I still haven't got an answer from Mario Blättermann and Znavko.
>
> I'm a bit worried that my messages ended up being filtered, as my mail server is so small. Can you try sending them something?

I’ve pinged them.

Thanks,
Ludo’.

Re: Translating the web site

[Ludovic Courtès]

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’.

Re: Translating the web site

[Julien Lepiller]

Le 5 octobre 2020 08:17:59 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>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.

Done, they're waiting for the copyright fixes.

>
>  2. Registration at fedora-project.org.
Done, but they're waiting for the repo above

>
>  3. Publicity so we actually get translations.
>
>Is that correct?
>
>I can help with #1, that’s my contribution.  :-)
>
>Thanks,
>Ludo’.

Re: Translating the web site

[Ludovic Courtès]

Hi again,

Julien Lepiller <julien@lepiller.eu> skribis:

> Le 5 octobre 2020 08:17:59 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :

[...]

>>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.
>
> Done, they're waiting for the copyright fixes.

Something I must have misunderstood: this repo will contain all the POT
files, not just those for the web site?

Ludo’.

Re: Translating the web site

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Yes, I think the goal is to translate everything through weblate, right?

Le 12 octobre 2020 08:29:32 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hi again,
>
>Julien Lepiller <julien@lepiller.eu> skribis:
>
>> Le 5 octobre 2020 08:17:59 GMT-04:00, "Ludovic Courtès"
><ludo@gnu.org> a écrit :
>
>[...]
>
>>>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.
>>
>> Done, they're waiting for the copyright fixes.
>
>Something I must have misunderstood: this repo will contain all the POT
>files, not just those for the web site?
>
>Ludo’.

[-- Attachment #2: Type: text/html, Size: 1364 bytes --]

Re: Translating the web site

[Ludovic Courtès]

PS: Please avoid top-posting.  :-)

Ludo’.

Sure, I don’t mind translating everything through Weblate eventually.
However, in the short term, could we simply push the web site POT files
to that repo on Savannah, so we can start getting translations for it?

It would be great to have more web site translations done by the time of
the release.

Julien Lepiller <julien@lepiller.eu> skribis:

> Yes, I think the goal is to translate everything through weblate, right?
>
> Le 12 octobre 2020 08:29:32 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>>Hi again,
>>
>>Julien Lepiller <julien@lepiller.eu> skribis:
>>
>>> Le 5 octobre 2020 08:17:59 GMT-04:00, "Ludovic Courtès"
>><ludo@gnu.org> a écrit :
>>
>>[...]
>>
>>>>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.
>>>
>>> Done, they're waiting for the copyright fixes.
>>
>>Something I must have misunderstood: this repo will contain all the POT
>>files, not just those for the web site?
>>
>>Ludo’.

Re: Translating the web site

[Joshua Branson]

I could help for #3.

I've been known to make videos.  If you guys want publicity for this,
would anyone want to be interviewed by me?  Maybe just a 10 minute
meet.jit.si interview talking about why guix is so cool, and why
translation of software is so vital.  I live in U.S., but I'm willing to
lose a little bit of sleep to get the word out.

Thanks,

Joshua

--
Joshua Branson
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
"You can have whatever you want, as long as you help enough other people get what they want." - Zig Ziglar

Re: Translating the web site

[Ludovic Courtès]

Hi,

Joshua Branson <jbranso@dismail.de> skribis:

> I could help for #3.
>
> I've been known to make videos.  If you guys want publicity for this,
> would anyone want to be interviewed by me?  Maybe just a 10 minute
> meet.jit.si interview talking about why guix is so cool, and why
> translation of software is so vital.  I live in U.S., but I'm willing to
> lose a little bit of sleep to get the word out.

That could be nice.  Likewise, I know Florian has already written a blog
post about this, which is “just” waiting for the translation process to
be set up.

Thanks,
Ludo’.

Manual license (was Re: Translating the web site)

[Miguel Ángel Arruga Vivas]

Hi, everybody!

Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> 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?

Sorry for bringing up this old issue so late, but I've just confirmed
that the sentence is enforced by TP's robot, as the pot file contains
literally this:
--
This file is distributed under the same license as the guix manual package.
--

Nonetheless I've tried to change the sentence in the po file to that and
it complained.  As the current phrasing is not really wrong (it says
guix package and the package includes the manual) I've sent the file
with these two lines instead:
--
This file is distributed under the same license as the guix package.
Note: The contents of this file are licensed under GNU FDL v1.3.
--

I hope this is enough clarification on the legal side.

Best regards,
Miguel

Re: Manual license (was Re: Translating the web site)

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

Thank you! I think it's alright (it says guix manual package because po4a enforces "package" at the end).

Le 11 octobre 2020 09:57:25 GMT-04:00, "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com> a écrit :
>Hi, everybody!
>
>Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>> 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?
>
>Sorry for bringing up this old issue so late, but I've just confirmed
>that the sentence is enforced by TP's robot, as the pot file contains
>literally this:
>--
>This file is distributed under the same license as the guix manual
>package.
>--
>
>Nonetheless I've tried to change the sentence in the po file to that
>and
>it complained.  As the current phrasing is not really wrong (it says
>guix package and the package includes the manual) I've sent the file
>with these two lines instead:
>--
>This file is distributed under the same license as the guix package.
>Note: The contents of this file are licensed under GNU FDL v1.3.
>--
>
>I hope this is enough clarification on the legal side.
>
>Best regards,
>Miguel

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.

[-- Attachment #2: Type: text/html, Size: 1814 bytes --]