all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.
Date: Mon, 11 Jan 2016 09:20:56 +0100	[thread overview]
Message-ID: <CAKrPhPPsXV6Y=ZFbB43ucutWFrCgqwW7AdZ0z82JL68k0UXkAg@mail.gmail.com> (raw)
In-Reply-To: <87wprhqb6v.fsf@gnu.org>

On Mon, Jan 11, 2016 at 12:14 AM, Mathieu Lirzin <mthl@gnu.org> wrote:
> Hi,
>
> Federico Beffa <beffa@ieee.org> writes:
>
>> HTML is not better than Info. Here we only need to keep it for
>> 'emacs-mit-scheme-doc' to work. This is functionality for mit-scheme
>> whereby Emacs looks up the documentation for the identifier at point.
>>
>> For PDFs, it depends on the type and quality of the manual. If it is
>> short and/or poor, then nobody will spend hours reading it. But if the
>> manual is good and long, then there is a chance that people will spend
>> a lot of time reading it and it would be nice to have a good quality
>> environment to read it (again, I'm talking about font graphics
>> rendering).
>>
>> This is analogous to making public buildings suitable for people with
>> wheel-chairs, ... may people don't care, until they are affected :-(
>
> Sorry I don't understand your analogy.  IIUC the discussion is about
> what should be installed with the default output.  Putting the PDF
> version of the manual in the 'doc' output will not prevent anyone to use
> it.  Did I miss something?

Well, the discussion is about this sentence:

   I just realized that its documentation is in Texinfo format.  What about
   simply installing the Info format like we do for other GNU packages, and
   not the PDF/PS/DVI version?

I can't find: why don't we put the PDF/PS/DVI in a different output.
If I misunderstood then my bad. But being less cryptic and more
explicit would prevent that.

Regards,
Fede

  reply	other threads:[~2016-01-11  8:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 17:33 [PATCH 5/6] gnu: mit-scheme: Generate and install documentation Federico Beffa
2016-01-05 22:13 ` Ludovic Courtès
2016-01-09 10:28   ` Federico Beffa
2016-01-09 18:42     ` Ludovic Courtès
2016-01-09 22:32       ` Federico Beffa
2016-01-10 18:50         ` Ludovic Courtès
2016-01-10 21:19           ` Federico Beffa
2016-01-10 23:14             ` Mathieu Lirzin
2016-01-11  8:20               ` Federico Beffa [this message]
2016-01-11  9:09             ` Ludovic Courtès
2016-01-11 11:58               ` Federico Beffa
2016-01-11 19:06                 ` Leo Famulari
2016-01-12  7:46                   ` Federico Beffa
2016-01-11 20:47                 ` Ludovic Courtès

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

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

  git send-email \
    --in-reply-to='CAKrPhPPsXV6Y=ZFbB43ucutWFrCgqwW7AdZ0z82JL68k0UXkAg@mail.gmail.com' \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=mthl@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.