From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Texinfo in descriptions?
Date: Wed, 22 Jul 2015 15:35:55 +0200
Message-ID: <87wpxs9ux0.fsf@gnu.org>
References: <87wpy0nygt.fsf@gmail.com> <87y4ige2ux.fsf@openmailbox.org>
	<87wpy0t83c.fsf@gnu.org> <87r3o7pz3h.fsf@openmailbox.org>
	<87y4ietrdz.fsf_-_@gnu.org> <874mkx8a5o.fsf@openmailbox.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45594)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ZHuBq-0000we-2J
	for guix-devel@gnu.org; Wed, 22 Jul 2015 09:36:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ZHuBi-00065H-HK
	for guix-devel@gnu.org; Wed, 22 Jul 2015 09:36:06 -0400
In-Reply-To: <874mkx8a5o.fsf@openmailbox.org> (Mathieu Lirzin's message of
	"Tue, 21 Jul 2015 23:37:23 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=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: Mathieu Lirzin <mthl@openmailbox.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>

Mathieu Lirzin <mthl@openmailbox.org> skribis:

> ludo@gnu.org (Ludovic Court=C3=A8s) writes:

[...]

> As much as I would appreciate texinfo markup in that context, I think it
> will still confuse our translator friends.  In=20
> (info "(gettext)Preparing Strings") we can found this:

[...]

> Sure HTML markup will not be pretty, but at least it will not encourage
> people to put lists everywhere (for example for listing features instead
> of describing what the package is doing).

Well, we can email the coordinator asking what they think of this.
Although not my favorite choice, HTML/XML would be fine too, as long as
we restrict ourselves to a clear subset.

(gnu.org actually uses the descriptions from the Womb (like we do), but
adds HTML markup in it:
<https://lists.gnu.org/archive/html/guix-devel/2014-01/msg00074.html>.)

> My secret dream is that descriptions (and their translation) would be
> managed directly in the FSD (Free Software Directory) so that we can
> import those directly and care only about the building and deployment
> process ;).

This has been discussed in the past (=E2=80=98TODO=E2=80=99 has an item abo=
ut it.)
Unfortunately, there is currently no way to do it automatically.  I=E2=80=
=99m
also not sure whether our criteria match theirs.

Thanks,
Ludo=E2=80=99.