Thanks for clearly presenting the various options. On 7 November 2016 at 15:52, Per Bothner <p...@bothner.com> wrote: > I don't think we settled on "best practices" for the image naming. > > (1) Should figure BAR.png in manual FOO be installed as: > (a) FOO-figures/BAR.png or: > (b) FOO-BAR.png > > Another option is a figures directory shared among many packages:
My understanding is that it is (a). > (2) Should the FOO.texi source refer to this match following the > installation location, respectively: > (a) @image{FOO-figures/BAR) or: > (b) @image{FOO-BAR} or: > (c) @image{figures/FOO-BAR} > Again (a). That's my understanding of it, anyway. (I got this wrong before.) > or should the source be plain: > > (d) @image{BAR} > In case (d) makeinfo needs to do the filename mapping. This could be nice, but there is no support for it at present. > (Having the info reader to the mapping is a bad idea > because the we have to use different conventions for html.) > > I'm fine with any of these, though (2d) requires someone to > do the work in makeinfo. Picking (1a/2a) or (1b/2b) or > (1c/2c) is mainly a matter of updating the documentation. Yes, the documentation could be a bit clearer.