EPUB transformations should copy SVG to images folder

Are you missing a feature? Request it's implementation here.
burbles
Posts: 37

EPUB transformations should copy SVG to images folder

Mon Aug 05, 2013 1:55 pm

I'd like to request that EPUB transformations should copy any SVG files defined with <object> or <image>, into an "images" folder. This request follows on from the post:
post27600.html#p27600
where I was using a DITA Map EPUB transformation where topics had links to valid SVG files. The images folder was created, but SVG files were not copied to that folder. This is not consistent behavior with transformations for WebHelp and WebHelp Mobile, which do copy SVG files.
Thankyou
sorin_ristache
Posts: 4144

Re: EPUB transformations should copy SVG to images folder

Mon Aug 05, 2013 2:12 pm

Hi,

Would you please add this request to the dita4publishers project? That is the place where this DITA-OT plugin is developed and where you are likely to receive a faster and more informed reply. Any future enhancements that the dita4publishers project owners decide to add will be also included in the dita4publishers plugin in a future version of the DITA-OT that comes in the Oxygen install kit.


Regards,
Sorin
Radu
Posts: 5987

Re: EPUB transformations should copy SVG to images folder

Wed Aug 07, 2013 5:13 pm

Hi,

The problem is that even if you add in one of the HTML documents which compose the EPUB the construct:

Code: Select all

<object data="../images/test.svg" type="image/svg+xml"/>


and you also add the image to the EPUB in the right place, some (maybe all) EPUB readers (Adobe Digital Editions in my case) will still not render it.
You can try this for yourself, open the EPUB in Oxygen's Archive Browser view, modify one of the HTML files to point to the image using the object construct and add to the EPUB the image in the images folder.

From what I've tested the only way to make my EPUB reader render SVG was to have the SVG embedded in the HTML content by adding the <svg> XML content content directly in the HTML content.
And there is a bug already added for this on the DITA For Publishers Project:

https://sourceforge.net/p/dita4publishers/bugs/50/

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

Return to “Feature Request”

Who is online

Users browsing this forum: No registered users and 0 guests