Re: docbook generation problem with @image

[Aharon Robbins]

Hi Karl.

> Separate from what you're actually reporting ...
>
>             @c FIXME: One day, it should not be necessary to have two cases,
>             @c but rather just the one without the "txt" final argument.
>
> I remember talking about this with you before, but not what the
> conclusion was (as usual).  If you're willing to assume current
> makeinfo, it should work, that is, presuming the behavior is acceptable
> to you (from the Image Syntax node in the manual):
>
>       In Info output, 'makeinfo' writes a reference to the binary image file
>     (trying FILENAME suffixed with 'EXTENSION', '.EXTENSION', '.png', or
>     '.jpg', in that order) if one exists.  It also literally includes the
>     '.txt' file if one exists.  This way, Info readers which can display
>     images (such as the Emacs Info browser, running under X) can do so,
>     whereas Info readers which can only use text (such as the standalone
>     Info reader) can display the textual version.

We did discuss it, and the new makeinfo and info behave well. The catch
is the "If you're willing to assume current makeinfo", which, sadly, I'm not.
The new makeinfo is considerably slower, and for straight Info generation
I prefer the old one, which is what's in /usr/bin on my Ubuntu dist.

At some point, I'll move to a dist which ships Texinfo 5.x and then
I'll simplify the gawk doc.  For now I can live with it.

Thanks,

Arnold