From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: info invisible changes Date: 13 Nov 2002 15:37:49 +0100 Sender: emacs-devel-admin@gnu.org Message-ID: <5xy97xsfgi.fsf@kfs2.cua.dk> References: <200211011623.gA1GNAL03601@rum.cs.yale.edu> <5xznsnvabl.fsf@kfs2.cua.dk> <200211061511.gA6FBfL02691@rum.cs.yale.edu> <5xfzu79jxp.fsf@kfs2.cua.dk> <5xbs4v9hq5.fsf@kfs2.cua.dk> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1037201072 20309 80.91.224.249 (13 Nov 2002 15:24:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 13 Nov 2002 15:24:32 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18BzC4-00042q-00 for ; Wed, 13 Nov 2002 16:12:40 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18BzO1-00066k-00 for ; Wed, 13 Nov 2002 16:25:01 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 18BxwP-00070w-00; Wed, 13 Nov 2002 08:52:25 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 18BxiX-0006A0-00 for emacs-devel@gnu.org; Wed, 13 Nov 2002 08:38:05 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 18BxiR-000688-00 for emacs-devel@gnu.org; Wed, 13 Nov 2002 08:38:04 -0500 Original-Received: from mail.filanet.dk ([195.215.206.179]) by monty-python.gnu.org with esmtp (Exim 4.10) id 18BxiQ-00067Y-00 for emacs-devel@gnu.org; Wed, 13 Nov 2002 08:37:59 -0500 Original-Received: from kfs2.cua.dk.cua.dk (kfs2.local.filanet.dk [192.168.1.182]) by mail.filanet.dk (Postfix) with SMTP id 52E207C017; Wed, 13 Nov 2002 13:37:56 +0000 (GMT) Original-To: bob@rattlesnake.com In-Reply-To: Original-Lines: 100 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:9345 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:9345 "Robert J. Chassell" 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 http://www.cua.dk