From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:32844) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iAWng-000397-O1 for guix-patches@gnu.org; Wed, 18 Sep 2019 06:03:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iAWne-0004oQ-Kz for guix-patches@gnu.org; Wed, 18 Sep 2019 06:03:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44802) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iAWne-0004oK-He for guix-patches@gnu.org; Wed, 18 Sep 2019 06:03:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iAWne-0002gS-9c for guix-patches@gnu.org; Wed, 18 Sep 2019 06:03:02 -0400 Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <87sgow0w7w.fsf@gnu.org> <20190916234941.1c450890@sybil.lepiller.eu> <20190916225258.yd4uzgcm4lyr5zgz@pelzflorian.localdomain> <87improzwm.fsf@gnu.org> <20190917133307.lhsouulr5yynzzrd@pelzflorian.localdomain> <87blvjm485.fsf@gnu.org> <20190917142819.qk6thhoocnci6svn@pelzflorian.localdomain> <87ef0fkknq.fsf@gnu.org> <20190917174102.edmbljhpte5rklsr@pelzflorian.localdomain> <20190917202035.1e2e5515@sybil.lepiller.eu> <20190917194415.ripfxwfmpx337z4d@pelzflorian.localdomain> Date: Wed, 18 Sep 2019 12:02:05 +0200 In-Reply-To: <20190917194415.ripfxwfmpx337z4d@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Tue, 17 Sep 2019 21:44:16 +0200") Message-ID: <87woe5disi.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: "pelzflorian (Florian Pelz)" Cc: 37413@debbugs.gnu.org Hello, "pelzflorian (Florian Pelz)" skribis: > I did not want to slow down these useful patches; the news file and > its translations can remain as proposed by Ludo. How channel authors > translate their news file is their choice. > > I thought we can suggest channel authors to use one gettext PO file > containing translations for both the news file and package information > and submit it to the TP. We can provide scripts to convert to and > from a news file. Writing such scripts is not hard because PO files > use a simple format. Guix itself should use this process too. Ah OK. Having an optional add-on process to work with PO files would be nice too have. My concerns were about having PO files at the core of the news mechanism. If you=E2=80=99re fine with the news format as it is in this patch series, = then I guess we can go ahead and push the patches? > How about adding a comment to the POT file that we wish for > translators to prioritize and urgently add translations for news? Is > it really necessary to submit the entire Guix tarball to the TP for > updating news; I thought the tarball is just for convenience of > translators? I wonder what Benno or others from the TP think. My feeling is that this use case doesn=E2=80=99t correspond to what the TP = is about, but yeah, you could ask them. Also, =E2=80=9Curgently=E2=80=9D won=E2=80=99t work because they would have= to be manual intervention by at least two people before the info reaches translators: someone on the Guix side who=E2=80=99d submit a tarball (?) to the TP, and = the TP coordinator who=E2=80=99d notify translation teams. That=E2=80=99s anot= her reason why I=E2=80=99m skeptical about the applicability of this workflow for news. >> Using a PO file for news items seem a bit drastic too: a news item is >> not supposed to change, except maybe for a typo. >> > > PO files are simple and what the Translation Project=E2=80=99s translator= s are > used to. I do not understand how another format could be more > appropriate. It=E2=80=99s not so much about the format, but rather about the tooling and workflow. I do not see how to integrate gettext and everything that goes with it (PO files, compilation to .gmo, text domains, etc.) directly into this design. But like you wrote, we can add tools on top that would allow us to use PO files if we want to. Thanks, Ludo=E2=80=99.