unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: Formatting lists in descriptions
Date: Wed, 15 Jul 2015 16:28:55 +0200	[thread overview]
Message-ID: <87r3o9mr4o.fsf@gnu.org> (raw)
In-Reply-To: <78a9e9745e3448c0aaaea5a54de59fe9@exchsrv2.sgc.loc> (Malcolm Cook's message of "Tue, 14 Jul 2015 18:58:14 +0000")

"Cook, Malcolm" <MEC@stowers.org> skribis:

> Hi - I'm late to this discussion - not sure all the issues on the table - but how about deferring to markdown in such cases.

We could use a more advanced format.  In that case I would prefer sexps
(but they would not play well with i18n), or, if we use a text DSL,
Org-mode (which is potentially less expressive than arbitrary sexps.)

It’s not a choice that can be made lightly because it will impact
translators and we must make sure we can provide UIs that honor markup
appropriately.

I’m not completely sure it’s necessary though.  Thoughts?

Ludo’.

  reply	other threads:[~2015-07-15 14:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 17:41 [PATCH] gnu: Document xorg packages Alex Kost
2015-07-13 17:06 ` Ludovic Courtès
2015-07-14  8:32   ` Formatting lists in descriptions (was: [PATCH] gnu: Document xorg packages.) Alex Kost
2015-07-14 13:23     ` Formatting lists in descriptions Ludovic Courtès
2015-07-14 18:58       ` Cook, Malcolm
2015-07-15 14:28         ` Ludovic Courtès [this message]
2015-07-15 15:01           ` Alex Kost

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r3o9mr4o.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=MEC@stowers.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).