all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.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 10:09:50 +0100	[thread overview]
Message-ID: <87y4bwzdlt.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPO+B9Z29rKWd36Ck4--VgCkfQ4fd3ODuDOAazFArhd5jw@mail.gmail.com> (Federico Beffa's message of "Sun, 10 Jan 2016 22:19:00 +0100")

Federico Beffa <beffa@ieee.org> skribis:

> 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).

I agree that rendering is much better in PDF.

> This is analogous to making public buildings suitable for people with
> wheel-chairs, ... may people don't care, until they are affected :-(

I disagree with the analogy.  On a computer, I find it simply less
convenient to browse PDFs than to browse Info, and that outweighs the
better rendering quality.  (As it turns out, Info is also much more
usable for people using a Braille reader.)

When I want to read a complete manual, I prefer the paper version,
though.

> 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.

You mean systematically?

There are several reasons Guix does not systematically provide PDF
manuals for GNU packages:

  1. We follow the GNU Standards, which is that ‘make install’ installs
     only Info by default.

  2. There would be technical complications with building PDFs
     systematically (TeX Live is huge, has a lot of dependencies, etc.)

  3. PDFs are quite big and (so I thought) inconvenient when reading on
     a screen, though I now understand that not everyone feels the same.

  4. Until now there hasn’t been demand for it.

So, back to MIT Scheme, what about adding PDFs in a “doc” output, and
installing Info only in “out”?

Regarding the rest of GNU packages, I’m very much in favor of the status
quo, possibly with exceptions like this on a case-by-case basis.

Let me know if you think this is not explicit enough!

Thanks,
Ludo’.

  parent reply	other threads:[~2016-01-11  9:09 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
2016-01-11  9:09             ` Ludovic Courtès [this message]
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=87y4bwzdlt.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@ieee.org \
    --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 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.