unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: info invisible changes
Date: Wed, 13 Nov 2002 18:20:15 +0000 (UTC)	[thread overview]
Message-ID: <m18C27b-000IeIC@localhost> (raw)
In-Reply-To: <5xy97xsfgi.fsf@kfs2.cua.dk> (storm@cua.dk)

   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

  reply	other threads:[~2002-11-13 18:20 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
2002-11-13 18:20                       ` Robert J. Chassell [this message]
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=m18C27b-000IeIC@localhost \
    --to=bob@rattlesnake.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).