unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
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 14:06:15 -0500	[thread overview]
Message-ID: <20160111190615.GA7019@jasmine> (raw)
In-Reply-To: <CAKrPhPPdA6=S9SMLGJcXM9_sirCsTNyw-_AxWQVv49kbZvttAw@mail.gmail.com>

On Mon, Jan 11, 2016 at 12:58:41PM +0100, Federico Beffa wrote:
> On Mon, Jan 11, 2016 at 10:09 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> > 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.
> 
> It seems you don't get that my point is not about personal preferences
> or feelings. It's about physical impairments (and there are plenty of
> shades of grays between good sight and completely blind, where big,
> good quality fonts matter).

Agreed, I know two people with very severe visual impairments who find
it more effective to magnify text to what seems an extreme degree than
to use a Braille reader.

> 
> I will install PDFs in a separate output.
> 
> Regards,
> Fede
> 

  reply	other threads:[~2016-01-11 19:06 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
2016-01-11 11:58               ` Federico Beffa
2016-01-11 19:06                 ` Leo Famulari [this message]
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=20160111190615.GA7019@jasmine \
    --to=leo@famulari.name \
    --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 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).