From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:52519) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iAETX-0002bq-18 for guix-patches@gnu.org; Tue, 17 Sep 2019 10:29:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iAETV-0006pm-VH for guix-patches@gnu.org; Tue, 17 Sep 2019 10:29:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44297) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iAETV-0006ph-S8 for guix-patches@gnu.org; Tue, 17 Sep 2019 10:29:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iAETV-0004fQ-LK for guix-patches@gnu.org; Tue, 17 Sep 2019 10:29:01 -0400 Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism Resent-Message-ID: Date: Tue, 17 Sep 2019 16:28:19 +0200 From: "pelzflorian (Florian Pelz)" Message-ID: <20190917142819.qk6thhoocnci6svn@pelzflorian.localdomain> References: <20190915221021.4165-1-ludo@gnu.org> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87blvjm485.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 37413@debbugs.gnu.org On Tue, Sep 17, 2019 at 03:39:38PM +0200, Ludovic Courtès wrote: > "pelzflorian (Florian Pelz)" skribis: > > You mean it takes too long for the TP coordinator to accept new > > versions of PO files? > > I mean two things: (1) there will not be PO files (see the format of > news entries proposed in this issue), It is easy to write a Guile script that prints a PO file with the news file content inserted as the msgid of a single entry, if xgettext does not support this already. Then there would be two PO files, one for the news file and one for the package info, that could be concatenated by msgcat to a single file. Guix could ship with this tooling for channel authors and an explanation for how to submit the resulting POT file to the Translation Project. I think a single file is easier for translators to manage than two files and typically we’d want news files and packages to be translated by the same (group of) translator(s). > and (2) I think this is outside > the scope of the TP. > > Does that clarify? > > Ludo’. I do not see why such translation should be outside the scope of the TP? I can only think of the speed of POT file acceptance and PO file translators. I am unsure if setting up Guix’ own translation team would attract quicker translators than relying on the TP. Regards, Florian