Aspose.Imaging 3.8.0.0 determines a .Wmf file as Dicom

Aspose.Imaging Product Family
1

Hi,


We’ve recently updated to the latest version of the Aspose product family and figured out that Aspose.Imaging.Image.GetFileFormat(Stream input) returns Dicom for a .Wmf file thus breaking our existing logic and failing to perform a Wmf conversion in our solution.

Previous versions starting from 3.7.0.0 would return Undefined, and we would then compare the input stream for having a specific file type signature (e.g. var wmfSignature = new byte[] { 0xD7, 0xCD, 0xC6, 0x9A, 0x00, 0x00 }:wink: and proceed based on that.

So, the problem we see is that a .wmf file (we.ve tried different wmfs) is determined as being a Dicom.

Thanks,
2
Hi Ulrik,

Thank you for your inquiry.

We have investigated the issue. Initial investigation shows that the issue persists. The issue has been logged into our issue tracking system with ID IMAGINGNET-2028. Our product team will further look into it. We will update with the progress via this forum thread.

3

The issues you have found earlier (filed as IMAGINGNET-2028) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
4

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.