Hi, On Wed, Jun 10, 2009 at 9:15 AM, Jürgen Spitzmüller<[email protected]> wrote: >> Hope this does it, please report any further issues. > > It doesn't work yet. What it now correctly does is finding the image in the > working directory and converting it to png (btw, why is it needed to convert a > jpg to a png?)
No reason, just thought that nobody would embed jpgs in a LyX document. I was wrong! I will correct it for next version. > What it doesn't yet is inserting the absolute image path, i.e. > > <img class="embedded" src="/home/work/pic.png" alt="figure Crash_1.png" > width="527" height="134"/> > > instead of > > <img class="embedded" src="pic.png" alt="figure Crash_1.png" width="527" > height="134"/> Excuse my ignorance, but why should it do that? Let us follow the sequence of events and you tell me where I have it wrong. - A document is located at, say, /home/work/doc.lyx, referencing /home/work/pic.eps (as a relative path, i.e. "pic.eps"). - The document (not the image) is copied to /tmp/random/doc.lyx to convert to html. - eLyXer is run --directory /home/work. - eLyXer converts /home/work/pic.eps to /tmp/random/pic.png. - The generated html /tmp/random/doc.html references "pic.png". - The files doc.html _and_ pic.png are copied from /tmp/random to /home/work/doc_lyx/ - The user opens the newly created html file and sees a brand new image. Why does eLyXer have to reference the image at its original location /home/work/pic.eps? The generated file is not even going to be there. Besides, absolute paths are a no-no if the html file is to be published anywhere, or even moved within the hard disk. Thanks, Alex.
