Le mardi 15 décembre 2009 à 00:32 +0100, jema...@gnu.org a écrit :
That would make it difficult to decouple the manuals after they get
installed. Having gnupdf-arch.texi looking into gnupdf-arch-figures/
and gnupdf-hg.texi looking into gnupdf-hg-figures/ makes it possible
to
Le dimanche 13 décembre 2009 à 00:28 +0100, jema...@gnu.org 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.
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/?
That would make it
Maybe we should suggest the maintainers to follow the same convention
I added something to the Texinfo manual about it.
Thanks,
k
Maybe we should suggest the maintainers to follow the same convention
I added something to the Texinfo manual about it.
Super! Thanks :)
Hi Karl.
But I don't think install-info should go around rewriting the Info
content. That seems highly problematic to me.
The only practical workaround I can see is to name your directory
something like gnupdf-figures and install the images in your Makefile.
Ok, I will use that
Hello.
In GNU PDF we are including a lot of pictures in the documentation of
the project (the reference manual, architecture guide, etc). For each
picture we are including several files: figure.txt for info readers,
figure.png for html output and figure.eps for tex.
In the sources tree the
Hi Jose,
I don't have a good solution for this.
But I don't think install-info should go around rewriting the Info
content. That seems highly problematic to me.
The only practical workaround I can see is to name your directory
something like gnupdf-figures and install the images in your
