RE: [docbook-apps] mediaobject with base64 encoded image data

["Dominik Psenner" <dpsenner@gmail.com>]

>-----Original Message-----
>From: Jirka Kosek [mailto:jirka@kosek.cz]
>Sent: Tuesday, April 03, 2012 9:43 AM
>To: Dominik Psenner
>Cc: 'Bob Stayton'; docbook-apps@lists.oasis-open.org
>Subject: Re: [docbook-apps] mediaobject with base64 encoded image data
>
>On 3.4.2012 8:38, Dominik Psenner wrote:
>
>> I'm asking because I also thought about integrating base64-encoded
>imagedata
>> better into docbook by:
>>
>> 1) either creating a fresh new attribute like "src" on the <imagedata />
>tag
>> that could be passed on to the respective FO attribute "src" in the tag
>> <fo:external-graphic />.
>>
>> 2) or parsing the "fileref" attribute and don't wrap it in "url()" if it
>> starts with "imagedata".
>
>There is no need to change anything on DocBook side to support this.
>Simply put data: into fileref attribute.

That doesn't work together with the IBEX processor because "data:.." is
wrapped into "url(data:..)" and then the processor treats "data:.." as an
url, which it is not and thus the image is not rendered as the data of the
image can't be retrieved from the path "data:.." unless it exists by
coincidence.

>There migh be needed some small
>changes in XSL stylesheets in order to skip usual file path massaging.

That would be the template named "fo-external-image" in graphics.xsl, isn't
it?

>Also I think that even data: should be wrapped in url() otherwise it
>would be non-conforming to XSL-FO spec.

At least the implemented IBEX interpretation of the XSL-FO spec doesn't
behave like that.

Cheers,
Dominik