unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: info invisible changes
Date: Tue, 12 Nov 2002 12:28:49 -0500 (EST)	[thread overview]
Message-ID: <m18BeqH-000IeBC@localhost> (raw)
In-Reply-To: <5xbs4v9hq5.fsf@kfs2.cua.dk> (storm@cua.dk)

    BTW, I was asked to implement image support in Info mode.  Has
    anyone done some thoughts on how that should work ....

As a first step, please display the images in the Info file in the
places corresponding to their locations in the Texinfo source, rather
than in some other place.  W3 mode, for example, puts images from the
beginning of an HTML file at the end of the buffer, and vice-versa;
and it drops some images.

Also, when you implement images, please consider additions that may be
made later:

  * An option to present the alternative text rather than the image so
    that the blind can listen to it.  (By blind, I mean people who
    listen to Info as they drive a car, the `situationally blind', as
    well as the permanently blind).

    Note that Emacspeak works well and no longer requires special
    text-to-speech hardware.  I run Emacspeak on this computer on
    which I am writing this using its built-in audio device and free
    software (the Debian `flite', `eflite', and `emacspeak' packages).

    The alternative text will come from the Texinfo source.  Such text
    is already an optional argument to the @image command.

  * The caption text and figure reference for the image.  The TeX for
    this could be taken from the botex.tex sources from 1985, since
    that (print-only) predecessor to Texinfo possessed images with
    captions and cross references to them.  But makeinfo and Info will
    need new code to handle these features, and the @image command
    will need additional options to hold them.

  * An option to put a user-inspired border around images, with a
    local variable, so you can specify it on a per-info file basis.
  
    Many images are plain and look terrible if shown flat against
    whatever background your instance of Emacs is using.  (For
    example, my current background is "DodgerBlue4"; to look good,
    most images need to be set off from that background a little by
    `picture frames' or borders.)

  * An option to load a background as you might for HTML.  Although
    people have complained heavily about Web pages that are unreadable
    because of their backgrounds, some backgrounds do nicely and
    should become a part of Emacs.  

    For examples, look at my Web site

        http://www.teak.cc

    [note the .cc extension] and at my neice's Web site

        http://www.goldenhillfarm.com

    in a Web browser, such as galeon, that shows backgrounds.

    In any event, I presume that Texinfo will eventually support
    backgrounds for its HTML output; Info might as well be ready to do
    the same.

  * An option to increase or decrease the size of the image.
    Different instances of Emacs use different resolution screens.  On
    a high resolution screen, for example, it is hard to read a font
    that is big enough on a low resolution screen.  It is the same
    with images.  An image that looks great on a generic personal
    computer screen looks too small on a high resolution personal
    computer screen.

    Obviously, Info is not bothered by the font size problem, since
    that issue is already solved; but will suffer an image size
    problem.

-- 
    Robert J. Chassell                         Rattlesnake Enterprises
    http://www.rattlesnake.com                  GnuPG Key ID: 004B4AC8
    http://www.teak.cc                             bob@rattlesnake.com

  reply	other threads:[~2002-11-12 17:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  8:04 info invisible changes Miles Bader
     [not found] ` <200211011623.gA1GNAL03601@rum.cs.yale.edu>
2002-11-05  4:08   ` Miles Bader
2002-11-05 18:49     ` Stefan Monnier
2002-11-07  4:49       ` Richard Stallman
2002-11-05 23:57     ` Kim F. Storm
2002-11-06  9:51       ` Miles Bader
2002-11-06 12:46         ` Kim F. Storm
2002-11-06 12:30           ` Miles Bader
2002-11-06 15:11         ` Stefan Monnier
2002-11-06 16:32           ` Miles Bader
2002-11-07 15:08           ` Richard Stallman
2002-11-12 10:11             ` Kim F. Storm
2002-11-12  9:22               ` Miles Bader
2002-11-12 10:59                 ` Kim F. Storm
2002-11-12 17:28                   ` Robert J. Chassell [this message]
2002-11-13 14:37                     ` Kim F. Storm
2002-11-13 18:20                       ` Robert J. Chassell
2002-11-14 12:17                         ` Richard Stallman
2002-11-14 21:38                           ` Kim F. Storm
2002-11-12 18:49               ` Stefan Monnier
2002-11-13 23:31                 ` Kim F. Storm
2002-11-14  0:39                 ` Kim F. Storm
2002-11-14  4:09               ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-11-14 13:57 Karl Berry

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=m18BeqH-000IeBC@localhost \
    --to=bob@rattlesnake.com \
    --cc=emacs-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/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).