Thanks Thomas. It appears to be a problem with the way the image was being encoded. I am using Batik's org.apache.batik.util.Base64EncoderStream to do the job, and it looks like (prepare to be blinded by a flash of the obvious) the stream must be closed in order for the remaining bytes to be written. I am unable to test this theory right now, but I'm inclined to believe it's the source of the problem. It's either that or little green gremlins have infested my machine, which I suppose is just as likely...
-----Original Message----- From: Thomas E Deweese [mailto:thomas.deweese@;kodak.com] Sent: Wednesday, November 13, 2002 2:36 PM To: Batik Users Subject: RE: Bugzilla Defect #14258 >>>>> "MG" == Michael Gale <[EMAIL PROTECTED]> writes: MG> I have attached the SVG document to generate the error using Batik MG> v1.5 b4. It should also be noted that once the exception is MG> thrown, no other SVG document can be opened from that point MG> onward. MG> The attached file will display a rectangle initially, and when the MG> user clicks within the shape, it should switch to the image. I MG> have tested it with Adobe's plug-in and it seems to work as MG> expected. MG> Let me know if you need anything else. Thanks for putting togeather the test. Well, it appears that the JPEG is truncated, it isn't clear if this is due to the base 64 data being truncated as well (I suspect it is as most b64 data has some '=' at the end to fill out the triplet and your example doesn't have this - but this is far from conclusive). To test this I replaced your b64 image with one I generated (using mmencodee on UNIX), and your test worked fine (my update is attached) I'm guessing Adobe is just being more forgiving of errors. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
