unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jambunathan K <kjambunathan@gmail.com>, emacs-devel@gnu.org
Subject: Re: C-h r and Images
Date: Mon, 02 Sep 2013 08:28:51 -0700	[thread overview]
Message-ID: <5224AEB3.5000508@cs.ucla.edu> (raw)
In-Reply-To: <831u57e089.fsf@gnu.org>

Eli Zaretskii wrote:
>> > Is it because the Info browser doesn't support it.
> Of course, it does!  Try reading the GnuTLS Info manual, for example.

I just now tried that, and it didn't work for me.
I visited (gnutls)TLS layers, and it said "[broken image]"
instead of showing an image for Figure 3.1.  This is on
Fedora 19 x86-64.

Perhaps this is a problem with that distribution,
or perhaps with Emacs on GNUish platforms, but either
way I'm pretty sure that images won't work with the
standalone info viewer.

Furthermore, images won't work well for users who have
trouble seeing -- not only the 100% blind, but those who
have age-related macular degeneration and similar problems.
These people often use screen readers such as Orca, and so
can grok text fairly well, but the images' contents will
be difficult for them to see, or may be invisible to them.

For all these reasons, images in technical manuals should
generally not be the sole source of information that
they contain.  It's definitely OK to have images, but
there should be an alternative way of getting the gist
of any technical information that an image conveys.
Unfortunately, that doesn't appear to be
true for the GnuTLS manual, at least not if my cursory
examination of Figure 3.1 is correct.



  reply	other threads:[~2013-09-02 15:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 14:14 C-h r and Images Jambunathan K
2013-09-02 15:01 ` Eli Zaretskii
2013-09-02 15:28   ` Paul Eggert [this message]
2013-09-02 15:38     ` Eli Zaretskii
2013-09-02 15:40       ` Eli Zaretskii
2013-09-02 21:34         ` Paul Eggert
2013-09-03  2:43           ` Eli Zaretskii
2013-09-03  3:18             ` Stephen J. Turnbull
2013-09-09 10:03           ` Stephen Berman
2013-09-09 14:07             ` Stefan Monnier
2013-09-09 15:03               ` Stephen Berman
2013-09-09 15:01             ` Andreas Schwab
2013-09-09 15:06               ` Stephen Berman
2013-09-16 12:11             ` Per Starbäck
2013-09-02 16:11       ` Eli Zaretskii
2013-09-02 15:44     ` Drew Adams
2013-09-02 16:10       ` Eli Zaretskii
2013-09-02 17:31     ` Jambunathan K
2013-09-02 17:41       ` Eli Zaretskii
2013-09-02 18:34         ` Jambunathan K
2013-09-02 18:10       ` Drew Adams
2013-09-02 19:37         ` Juri Linkov
2013-09-02 20:16           ` Drew Adams
2013-09-03  2:37           ` Kanthimathi R
2013-09-03  8:56         ` Xue Fuqiao
2013-09-03 14:41           ` Drew Adams
2013-09-03 15:59           ` Eli Zaretskii
     [not found] <<87y57fe2ej.fsf@gmail.com>
     [not found] ` <<831u57e089.fsf@gnu.org>
     [not found]   ` <<5224AEB3.5000508@cs.ucla.edu>
     [not found]     ` <<4884857e-3cd1-4b47-9949-6919c60f2186@default>
     [not found]       ` <<83txi3cih5.fsf@gnu.org>
2013-09-02 17:02         ` Drew Adams
2013-09-02 17:39           ` Eli Zaretskii
     [not found]     ` <<878uzf5dvr.fsf@gmail.com>
     [not found]       ` <<50869c34-8cb2-477b-a6a8-a393abb76d12@default>
     [not found]         ` <<CAAF+z6EHgnt4Mbz8hHfv3csDUPYGvuNOQGKNB_AiNee7Umiahg@mail.gmail.com>
     [not found]           ` <<83ioyhdhg7.fsf@gnu.org>
2013-09-03 16:34             ` Drew Adams
2013-09-03 20:37               ` Juri Linkov
2013-09-04  5:47                 ` Eli Zaretskii
2013-09-04 22:38                 ` Xue Fuqiao
2013-09-04 22:41                   ` Xue Fuqiao
2013-09-05  7:07                   ` Eli Zaretskii
2013-09-06 10:53                     ` Xue Fuqiao
2013-09-06 12:16                       ` Eli Zaretskii
     [not found] <<372ba59c-42be-463c-a69f-6b910d8cc40e@default>
     [not found] ` <<83r4d7cecc.fsf@gnu.org>
2013-09-02 18:15   ` Drew Adams

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=5224AEB3.5000508@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kjambunathan@gmail.com \
    /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/emacs.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).