[EMAIL PROTECTED] (Karl Berry) writes:
Hi Karl,
> Excellent! Thanks for putting in this work.
[..]
> Here are some issues that come to mind with [image: /file/name] --
> I just checked, and the null/backspace combination does show up
Thanks for looking into this. So, there is reason to use the ^H (we
could also drop the '[' and ']'). This is what I used in for the next
version:
[EMAIL PROTECTED] [EMAIL PROTECTED]
where PARAMETER nor VALUE may contain a [EMAIL PROTECTED] Also, VALUE may not
a contain space or double quote, or VALUE is enclosed in double
quotes (using \" to escape). A typical tag would look like:
[EMAIL PROTECTED] src=/usr/share/doc/lilypond/example-1.png alt="Alt text
for text image browser"[EMAIL PROTECTED]
where the value of the ALT parameter contains the image's .TXT file.
Currently, only the 'src parameter is actually used.
> 5) It think it would be nice if it were at least possible to embed the
> actual images in the info file, instead of having to refer to
> external files. Perhaps a base64 or base95 encoding of the binary data?
Hmm, I'm not going to do this, primarily because I see not much reason.
Typically, all info documentation will also be present in HTML form
(on Debian GNU/Linux at least), so they should use the same (external)
image files.
> What do you (or anyone else...) think of all that?
I think I addressed most of your remarks in my next version:
http://lilypond.org/~jan/info-image
If this seems OK, I'll have a look at makeinfo to produce the image tags.
Greetings,
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
