On 10/17/2016 11:47 AM, Gavin Smith wrote:
On 16 October 2016 at 20:36, Per Bothner <p...@bothner.com> wrote:
Supposed my Kawa manual uses a picture pic1.png.

The texinfo manual says:

   If you want to install image files for use by Info readers too, we
   recommend putting them in a subdirectory like 'FOO-figures' for a
   package FOO.  Copying the files into '$(infodir)/FOO-figures/' should be
   done in your 'Makefile'.

This only discusses installation, but it seems to imply that the
texinfo source use:


which means this effects non-Info output as well.

Well, I'm not sure. I don't think it does imply that. The kawa-figures
directory would be for installation only. Thus, if you did do
@image{kawa-figures/pic1}, this might imply installation under
${infodir}/kawa-figures/kawa-figures, just as
@image{more-figures/pic2} might imply installation under

Well, either "kawa-figures" has to be in the @image command,
or one of makeinfo or info mode have to magically add it.

I see no evidence for the latter (in either info.el or from a simple

It appears to follow that if we want info-mode to display
${infodir}/kawa-figures/pic1.png, then the texinfo source
has to say @image{kawa-figures/pic1} .  How also would it work?

 Also, I'm not sure if it's right
to have directories in the argument to @image at all, although I
haven't tried it and maybe it works perfectly.

'make pdf' seems handle fine creating a pdf with images in a

I don't know about 'make dvi' - but who cares?

The reason is that the
file is processed as TeX and there are TeX systems for operating
systems with differing types of filesystem.

So?  Is there any currently-used system that can run TeX that wouldn't be
able to handle kawa-figures/pic1.png?  (I would not expect MS-Windows
to have any problems.  It's only the Windows shell that doesn't like
using slashes - most libraries work fine.)

It would be simpler just to have everything on the one level.

That appears inconsistent with the advice to use FOO-figures.
        --Per Bothner
p...@bothner.com   http://per.bothner.com/

Reply via email to