Adds support for inline images in the form of base64 encoded data urls. This is particularly useful for displaying FO files generated from Word docs. Requires commons-codec. For details of word to fo conversion see: http://www.microsoft.com/downloads/details.aspx?FamilyId=E0FAA0AF-A185-4296-B74D-A9FE870C92CC&displaylang=en For details of the data url scheme see: http://www.ietf.org/rfc/rfc2397
Created attachment 17334 [details] Patch for FOURIResolver
Created attachment 17335 [details] Test case with embedded image.
Richard, thanks for the patch. I'd prefer not to add a dependency on a whole new library for just one class. Would you mind rewriting your patch to use Batik's org.apache.batik.util.Base64DecodeStream? I'll gladly apply your patch then. Some time ago I also posted a generic solution to this problem, found here: http://marc.theaimsgroup.com/?l=fop-user&m=110875657902117&w=2 (Just for completeness) We might switch to Batik's ParsedURL infrastructure in the future which automatically gives us RFC2397 support, but your solution will certainly help in the meantime.
Created attachment 17336 [details] Updated patch using batik's decoder.
Thanks, Richard. That didn't take you long to change that patch. :-) Patch applied: http://svn.apache.org/viewcvs?rev=366184&view=rev Note to myself: Make sure the base64 stuff goes into Commons so we don't have a dependency on Batik in FOURIResolver in the long run.
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed