[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #35395] bad picture path with --html and --without --no-split

From: Vincent Belaïche
Subject: [bug #35395] bad picture path with --html and --without --no-split
Date: Mon, 30 Jan 2012 21:09:59 +0000
User-agent: Opera/9.80 (Windows NT 5.1; U; fr) Presto/2.10.229 Version/11.60

Follow-up Comment #4, bug #35395 (project texinfo):


I also think that absolute path don't make sense, because one likes to move a
manual around.

Also, you need to keep in mind that texi2any issues a warning when the image
file is not found, so when you run texi2any, you have an idea where is image
files are, and because you have this idea you are able to set the relative
paths to this files referred from the generated HTML location. Generally
speaking this simply consist in take the relative path as is with --no-split
option, and with ../ prefix without --no-split, as Karl suggested.

Concerning this I found another issue, let me tell you what. I want to
generate jPicEdt manual, and include it into the distribution jar file. So I
proceed as follows:

1. I first erase the whole content of directory

   please note that /jpicedt/distribution is the directory that is gneerated
and jarred to produce the distribution, so one destroys  /jpicedt/distribution
to rebuild all cleanly.

2. Then I copy all the pictures of interest into a new directory:

3. Then I run the following command:

   current directory = 

   command line =
    texi2any --html --no-split /jpicedt/source/help-files/fr.texi

  (fr.texi is the manual in French, and it contains some @image commands like
this @image{img/mypicture, ...}

texi2any does not bark that it does not find the picture files because it is
using the current directory for testing the file presence, and all the picture
are in currentdirectory/img, which is consistent with the @image{...} file

However the file fr.html is generated as /jpicedt/source/help-files/fr.html.
This is not consistent, it should have been generated as

What I am meaning is that if you test the file presence relative to some/place
, then you have to place the generated HTML in the same location some/place in
the case of --no-split, or in new directory some/place/fr and without
--no-split (when we have @setfilename fr.info). Otherwise does it make any
sense to test the presence relative to some/place. In other words, it should
be possible to configure some/place to be either the current directory or the
directory where the top texi source file is placed, but not to have some/place
have different values for different things.

Ok, this issue is not a big issue, because I can copy first fr.texi from
/jpicedt/source/help-files/ to /jpicedt/distribution/help-files/, and then run
the command.

   current directory = 

   command line =
    texi2any --html --no-split fr.texi

and then erase fr.texi



Reply to this item at:


  Message posté via/par Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]