Le dimanche 13 décembre 2009 à 00:28 +0100, [email protected] a écrit : > Ok, I will use that workaround, maintaining several sub directories in > doc/ for the different manuals.
This sounds suboptimal. Can't you use a common figures directory with a
name that includes the name of your package, e.g. gnupdf/ or
gnupdf-figures/?
> Maybe we should suggest the maintainers to follow the same convention
> too? As time passes more and more projects would want to deploy the
> images for graphics-enabled info readers...
For LilyPond info documentation, "make install-doc" creates
${info_dir}/lilypond/, which is a symlink to the subdirectory of
isntalled HTML docs tree which contains the images.
Best
--
John Mandereau
signature.asc
Description: Ceci est une partie de message numériquement signée
