From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Robert J. Chassell" Newsgroups: gmane.emacs.devel Subject: Re: info invisible changes Date: Wed, 13 Nov 2002 18:20:15 +0000 (UTC) Sender: emacs-devel-admin@gnu.org Message-ID: 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> <5xy97xsfgi.fsf@kfs2.cua.dk> Reply-To: bob@rattlesnake.com NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1037214244 25837 80.91.224.249 (13 Nov 2002 19:04:04 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 13 Nov 2002 19:04:04 +0000 (UTC) Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18C2nw-0006hv-00 for ; Wed, 13 Nov 2002 20:04:00 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18C2zx-0003po-00 for ; Wed, 13 Nov 2002 20:16:25 +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 18C2HY-0005rT-00; Wed, 13 Nov 2002 13:30:32 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 18C27z-0003Qg-00 for emacs-devel@gnu.org; Wed, 13 Nov 2002 13:20:39 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 18C27v-0003Pu-00 for emacs-devel@gnu.org; Wed, 13 Nov 2002 13:20:38 -0500 Original-Received: from megalith.rattlesnake.com ([140.186.114.245] helo=localhost) by monty-python.gnu.org with esmtp (Exim 4.10) id 18C27u-0003Pn-00 for emacs-devel@gnu.org; Wed, 13 Nov 2002 13:20:34 -0500 Original-Received: by rattlesnake.com via sendmail from stdin id (Debian Smail3.2.0.114) Wed, 13 Nov 2002 18:20:15 +0000 (UTC) Original-To: emacs-devel@gnu.org In-reply-to: <5xy97xsfgi.fsf@kfs2.cua.dk> (storm@cua.dk) 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:9398 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:9398 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) ? The Solfege music program contains @image command in its `online-docs/C/music-format.texi' file. I have version 1.4.3, but the latest version is 1.9.2: http://prdownloads.sourceforge.net/solfege/ solfege-1.9.2.tar.gz or solfege-1.9.2-1.src.rpm The download is not quite 400kb. The @image commands contain only one argument like this: @image{../png/simple} The images are in PNG format. They display well in the HTML files in Galeon. Unfortunately, I could not build an Info file out of the Texinfo file; the distribution lacks a .txt file for `makeinfo' to use: $ makeinfo music-format.texi music-format.texi:33: @image file `../png/simple.txt' (for text) unreadable: No such file or directory. Also, the emacs/lispintro/ directory in the current CVS for GNU Emacs 21 contains EPS files for @image commands in emacs/lispintro/emacs-lisp-intro.texi. The @image commands are within @tex ... @end tex environments. Plain text diagrams are included within the Texinfo file for Info, HTML, and for printers that cannot handle EPS, although nowadays, `makeinfo' can handle plain-text .txt files. @tex @image{cons-1} @end tex Again, the @image commands contain only one argument even though the current @image command can hold up to 4 more arguments: @image{FILENAME, [WIDTH], [HEIGHT], [ALTTEXT], [EXTENSION]} These are the only two Texinfo files that I know about that contain @image, although I am sure there must be others. Still, I am not surprised. The people writing in Texinfo have been mindful of their potential audience, and understood that it includes those who work over very slow connections and those who cannot see. > 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? Initially, perhaps it should follow the image as if it were a caption. I think that eventually, a user should be able to toggle among the three states: image, alt-text, both Emacs already allows image borders, so an Info customization would be ok here. Good! I never realized that! That would make a nice option. -- Robert J. Chassell Rattlesnake Enterprises http://www.rattlesnake.com GnuPG Key ID: 004B4AC8 http://www.teak.cc bob@rattlesnake.com