From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brandon Invergo Subject: Re: Synchronizing descriptions with GSRC? Date: Tue, 08 Oct 2013 23:45:11 +0200 Message-ID: <8738obphco.fsf@naga.invergo.net> References: <8738rm9lz5.fsf@gnu.org> <87d2qqp0j7.fsf@naga.invergo.net> <87hag26pis.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39288) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTf5q-0000Bc-8O for guix-devel@gnu.org; Tue, 08 Oct 2013 17:45:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VTf5h-00074U-R8 for guix-devel@gnu.org; Tue, 08 Oct 2013 17:45:26 -0400 In-Reply-To: <87hag26pis.fsf@gnu.org> ("Ludovic =?utf-8?Q?Court=C3=A8s=22'?= =?utf-8?Q?s?= message of "Thu, 11 Jul 2013 00:03:55 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, bug-gsrc@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ludovic et al, >> Perhaps it would be best to keep all canonical package descriptions, >> short and long, in a single file under revision control somewhere, such >> as in womb. They would then be available for anyone who needs them, >> should any need arise in the future and it would be easier for all >> involved to stay in sync. What do you think? > > Sounds good to me. OK, I've finally gotten around to moving package descriptions (long and short) to a file in Womb (gnumaint/pkgdescr.txt). The file is recutils-compatible.=20=20 Currently, all of the long descriptions ("blurbs") are taken from GSRC. Between Karl and I, we're currently in agreement that writing/adapting new descriptions for all of the packages is better than straight copying From=20websites/READMEs, mainly for keeping a certain level of consistency (length, style, level of detail, etc.) between the descriptions. It also avoids any potential copyright problem, no matter how unlikely it may be. In addition to Guix and GSRC, these descriptions will also be used to provide descriptions for featured packages on gnu.org, so they can't be too long. The file is fresh out of the oven, so there may be some changes after Karl reviews it. But anyway, it's there as a starting point. > A related question is i18n: Guix uses gettext, and the plan is to use > the Translation Project for the translation of synopses/descriptions > too. Should that be handled externally too? If it is, we=E2=80=99d stil= l need > to have a gettext catalog for our purposes. How could that work? This is still something to work out. Should the transltion be done in Womb? Can those be extracted easily for use in Guix? I have no idea. But again, at least we have a starting point now. Cheers, =2Dbrandon --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJSVHzpAAoJEARu3ubrerdNFTUIAL9ZVK49Vfn+ta0z0ag4qyiD +2B7sRSh4hHUu4BvtxJiJ7I96QzHVIQH0VRXDa2Mvz2fnIuVzO9JBXHh8YtYiOIN ttJYT3cbZd52OS+r7GSdQxEtE45hIxX91bIPXn7Co+ksjfxmmAuNOS5SRDfavqp4 1tSZxwKMbne9LE69SknsLlPvjKvJwOlTlvdrzjtakpxxYS54WOo66a2+AgiLZB6W sJtwYRXyTMu4xgei69ON8eFEqj8/K25Rju2Yw7URv2/ozw3oc6xEuIhh8Rlr+f1w iWvRcAe80A5BxcsHYyn+147pZ/ajNDg1NDYPhlQf2aOu+qopwLEw3mBJi32dJ58= =ewZX -----END PGP SIGNATURE----- --=-=-=--