unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.
Date: Sun, 10 Jan 2016 22:19:00 +0100	[thread overview]
Message-ID: <CAKrPhPO+B9Z29rKWd36Ck4--VgCkfQ4fd3ODuDOAazFArhd5jw@mail.gmail.com> (raw)
In-Reply-To: <87bn8t5kw8.fsf@gnu.org>

On Sun, Jan 10, 2016 at 7:50 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Federico Beffa <beffa@ieee.org> skribis:
>> Texinfo is great for looking up pieces of information in a reference
>> manual.
>
> You mean Info, right?

yes.

>
>> However, when it comes to reading a sizable part, I much prefer PDFs
>> with a much superior graphic quality and scaling capability and would
>> like to keep it (my eyes aren't in great conditions). I think we can
>> drop PS. DVI is not installed. HTML is required by
>> 'emacs-mit-scheme-doc'.
>
> One can choose the font family and size for Info documents viewed in
> Emacs (or even in a terminal.)  :-)  I find that Info is much more
> convenient when reading on a computer because of its interface to
> navigate the document, search the indexes, and search for words.

I know that you can choose font and size in emacs and console. But the
fact stays that the rendered quality difference is very large. I do
not know what to add... Many peoples claim not to see much difference.
I and some friends do see a large difference. Obviously the
visual-system varies a lot between peoples.

As said, I agree that for looking up reference information the Info
format is pretty good.

>
> The thing is, we could make an exception for MIT Scheme and provide PDF
> and/or HTML in addition to Info.
>
> However, what should we do with the whole set of GNU packages?  I’m
> very much in favor of keeping only Info by default, possibly with a few
> exceptions.

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 :-(

Regards,
Fede

  reply	other threads:[~2016-01-10 21:19 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 [this message]
2016-01-10 23:14             ` Mathieu Lirzin
2016-01-11  8:20               ` Federico Beffa
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

  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=CAKrPhPO+B9Z29rKWd36Ck4--VgCkfQ4fd3ODuDOAazFArhd5jw@mail.gmail.com \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).