https://issues.apache.org/bugzilla/show_bug.cgi?id=44886
Summary: Format of PICT records seems different to other metafile
blips
Product: POI
Version: 3.0
Platform: PC
OS/Version: Windows Vista
Status: NEW
Severity: normal
Priority: P2
Component: HSSF
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
Created an attachment (id=21864)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=21864)
Hex dump of PICT blip
Now that Bug 44857 is resolved and I can fully parse the Escher records in a
test file we happen to use in testing, I have been investigating the subtle
change in the MD5 of the returned data. The reason turned out to be obvious,
but it turns out the contents of the picture were unusable both before and
after as the format of the picture record is nonsense internally, or at least
it's nonsense when parsed as a WMF/EMF blip.
I've attachd a hex dump of the blip in question which has the header parsed out
by hand. The declared length of this blip I have already confirmed to be
correct, but as you can see the contents seem to be completely unrelated to the
code currently used for EMF and WMF, so the format must be something else
entirely.
The remaining data doesn't appear to contain a declaration of the length of
itself, so I've been wondering if perhaps it's an opaque blob of PICT data. I
don't know the format of PICT though so I can't confirm this right now.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
