forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: [jira] Commented: (FOR-872) Updated odt_to_xhtml.xsl to pass <title> & <h1> elements.
Date Wed, 10 May 2006 07:22:59 GMT
Clay Leeds wrote:
> On May 9, 2006, at 8:19 PM, Clay Leeds wrote:
>> On May 5, 2006, at 4:58 PM, David Crossley wrote:
>>> There is recent discussion in the mail archives about
>>> relative paths to images. It causes the problem that
>>> you refer to.
>>> -David
>> I think I found the thread[1]. But I don't think it helps much.
>> The images I'm 'referencing' are embedded in the ODT  
>> files.  I don't refer to them as 'images/blah.jpg'. I don't place  
>> them in 'xdocs/images/' or 'resources/images/' and then reference  
>> them using relative paths. I pasted the graphics into 
>> files. It is the Cocoon pipeline that is copying  them to 
>> build/images/ instead of build/site/images/. Cocoon copies  them from 
>> their embedded 'Pictures/' directory in the ODT 'zip'  file to 
>> build/images/blah.jpg instead of build/site/images/blah.jpg.
>> What I think I need to do, is modify the Cocoon pipeline to ensure  
>> images are copied from {$filename/Pictures/*.jpg} them to build/ 
>> site/images/*.jpg.
>> Even better--since, as I mentioned in my post, there might be a  
>> problem of having the same image name signify different images, it  
>> would be best to have the pipeline copy the files (and reference  
>> them!) to: build/site/images/$filename/*.jpg
>> [1]
>> [2]
> I am looking into this further. The PATH to the files in question are  
> defined in as:
> file:///Users/clay/Sites/myproject/src/documentation/content/xdocs/ 
> images/picture_01.jpg
> However, the images are embedded in the document as well (under  
> $filename.odt/Pictures/*.jpg). I might be able to reference the  images 
> in the document as '/images/picture_01.jpg' but then they will  no 
> longer show as an image in the OOo/OpenDocument file.

I recall struggling with this in the OOo plugin. I suggest you look at 
how images are handled in there.

(I would like to echo Ferdinands concerns about re-inventing the wheel 
with this new ODT plugin. We should have at least forked the OOo plugin 
to do this - too late now, but Clay, you should be aware many problems 
will already be solved in the OOo plugin).


View raw message