unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] gnu packages: Clean up synopses and descriptions.
Date: Sun, 19 Jul 2015 12:58:18 +0300	[thread overview]
Message-ID: <87h9p0o4ed.fsf@gmail.com> (raw)
In-Reply-To: <20150718211303.GA3038@debian> (Andreas Enge's message of "Sat, 18 Jul 2015 23:13:03 +0200")

Andreas Enge (2015-07-19 00:13 +0300) wrote:

> Coming late, I have not followed the full discussion closely, so my remark
> may be out of tune.

Not too late; the final decision on lists formatting has not been made
yet.  The last related post is Ludo's "Texinfo in descriptions?":
<http://lists.gnu.org/archive/html/guix-devel/2015-07/msg00471.html>.

> I think our descriptions should be formatted as simply
> as possible: just plain ascii text, which would work in any locale (or if
> you insist, maybe utf8).
>
> So far, I simply avoided lists in package descriptions; usually, by
> replacing
> "The bla package contains
> - A
> - B
> - C"
> by "The bla package contains A; B; C." or similarly.

This is good if A, B, C are not too long, but I think it is less
readable for more verbose list items (e.g., 'guile-json', 'xkb-utils',
'libdaemon', …).

-- 
Alex

  reply	other threads:[~2015-07-19  9:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 11:17 [PATCH] gnu packages: Clean up synopses and descriptions Alex Kost
2015-07-16  9:40 ` Eric Bavier
2015-07-16 15:55   ` Alex Kost
2015-07-16 19:08     ` Ludovic Courtès
2015-07-17 12:41       ` Alex Kost
2015-07-17 21:24         ` Ludovic Courtès
2015-07-18 10:07           ` Alex Kost
2015-07-16 11:52 ` Mathieu Lirzin
2015-07-16 15:50   ` Ludovic Courtès
2015-07-16 21:33     ` Mathieu Lirzin
2015-07-17 21:18       ` Texinfo in descriptions? Ludovic Courtès
2015-07-21 21:37         ` Mathieu Lirzin
2015-07-22 13:35           ` Ludovic Courtès
2015-07-22 21:24             ` Ludovic Courtès
2015-07-22 22:08               ` Andreas Enge
2015-07-23  9:49                 ` Mathieu Lirzin
2015-07-23 13:57                   ` Ludovic Courtès
2015-07-23 15:09                     ` Daniel Pimentel
2015-07-23 18:00                       ` Andreas Enge
2015-08-25 22:09                     ` Mathieu Lirzin
2015-08-26  7:57                       ` Andy Wingo
2015-08-27 19:48                         ` Mathieu Lirzin
2015-07-23 13:54                 ` Ludovic Courtès
2015-08-27 21:04               ` Mathieu Lirzin
2015-08-28 21:47                 ` Mathieu Lirzin
2015-08-30 17:23                   ` Ludovic Courtès
2015-08-30 19:06                     ` Alex Kost
2015-08-30 20:42                     ` Mathieu Lirzin
2015-08-31 21:21                       ` Ludovic Courtès
2015-09-01 16:41                         ` Mathieu Lirzin
2015-09-02 21:27                         ` Mathieu Lirzin
2015-09-03 22:12                           ` Ludovic Courtès
2015-09-04 19:43                             ` Mathieu Lirzin
2015-09-06 13:51                               ` Ludovic Courtès
2015-09-06 20:10                                 ` Alex Kost
2015-09-06 21:31                                   ` Ludovic Courtès
2015-09-07 15:50                                     ` Alex Kost
2015-09-07 15:59                                       ` Ludovic Courtès
2015-08-30 10:10                 ` Alex Kost
2015-08-30 12:24                   ` Mathieu Lirzin
2015-08-30 15:19                     ` Alex Kost
2015-07-17 12:35     ` [PATCHES] gnu packages: Clean up synopses and descriptions Alex Kost
2015-07-17 21:07       ` Mathieu Lirzin
2015-07-17 21:30       ` Ludovic Courtès
2015-07-18 10:08         ` Alex Kost
2015-07-18 21:13           ` Andreas Enge
2015-07-19  9:58             ` Alex Kost [this message]
2015-07-16 16:03   ` [PATCH] " Alex Kost
2015-07-16 20:02     ` Mathieu Lirzin

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=87h9p0o4ed.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=andreas@enge.fr \
    --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).