From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: info invisible changes
Date: 13 Nov 2002 15:37:49 +0100 [thread overview]
Message-ID: <5xy97xsfgi.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <m18BeqH-000IeBC@localhost>
"Robert J. Chassell" <bob@rattlesnake.com> writes:
> 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.
Of course, I didn't even imagine there was any other place...
Actually, I'm basically looking for the specification of how images
are supposed to be embedded in or referenced by info files (as a
result of using @image); something like *Image: file. or whatever...?
Does any of the info files provided on, say, a redhat 7.3 system
include images in the info files (so I have something to test on) ?
> 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.
I agree, but where is that text available in the generated info file?
>
> * 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.
Suggest that to the texinfo team -- once it is there, we can start
working on emacs support for it.
>
> * 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.)
>
Emacs already allows image borders, so an Info customization would be
ok here.
> * 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.
Emacs does not support background images, and neither does texinfo in
info files, so I prefer to delay the implementation until the features
are available.
>
> * 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.
>
Again, this seems to be generally useful. Maybe a separate TODO
item which can then be utilized by info once it is available.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-11-13 14:37 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
2002-11-13 14:37 ` Kim F. Storm [this message]
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=5xy97xsfgi.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--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).