From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:54075) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iAHUJ-0003GH-Mu for guix-patches@gnu.org; Tue, 17 Sep 2019 13:42:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iAHUI-0000uO-Er for guix-patches@gnu.org; Tue, 17 Sep 2019 13:42:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44395) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iAHUI-0000uJ-A5 for guix-patches@gnu.org; Tue, 17 Sep 2019 13:42:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iAHUI-0001VC-4u for guix-patches@gnu.org; Tue, 17 Sep 2019 13:42:02 -0400 Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism Resent-Message-ID: Date: Tue, 17 Sep 2019 19:41:02 +0200 From: "pelzflorian (Florian Pelz)" Message-ID: <20190917174102.edmbljhpte5rklsr@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> <20190917142819.qk6thhoocnci6svn@pelzflorian.localdomain> <87ef0fkknq.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87ef0fkknq.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 05:27:37PM +0200, Ludovic Courtès wrote: > As you’ve seen, the format I proposed does not rely on PO files and > gettext at all: > > https://issues.guix.gnu.org/issue/37413#5 > I did not read carefully before, but even with this format, a Guile script could turn it into a POT file with multiple entries and another Guile script could add translations from a PO file into such a news file. > Are you suggesting that it should rely on PO files? Yes. The format need not be changed. PO file conversion scripts can be added later, but should be a goal. > We can discuss it, > but that would be a significant change with technical challenges > compared to what I propose. > (Also keep in mind that the news mechanism > aims to be available to third-party channels as well.) > 3rd parties would not need to use the PO file conversion scripts. > Also, why do you mention “the package info”? There’s no notion of a > package here, so I wonder if there’s a misunderstanding. > Channels contain packages whose summaries and descriptions need translations as well, or do I misunderstand? Admittedly, it will take some time until guix-packages is translated, but it should be a goal. > >> 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. > > Speed would be a problem (POT files have to be manually accepted by > Benno.) But also, like I wrote earlier, (1) the TP is geared towards > translating releases of software packages, and (2) and those news > snippets could arrive anytime, not in sync with a “release.” > > > I am unsure if setting up Guix’ own translation team would attract > > quicker translators than relying on the TP. > > Yeah, having a real translation team is best, but in this case I don’t > see how that could work. > > Julien mentioned some time ago that we could run our own Pootle > instance. Maybe that could be helpful in this case. > > Thank you, > Ludo’. I do not know what Benno thinks about this. I would prefer this to be handled by some Translation Project eventually. Regards, Florian