Corel Draw (cdr)

Aspose.Imaging Product Family
1

Can Aspose.Imaging support writing xmp metadata to CorelDraw(cdr) file?

2

@3stan

Summary
Aspose.Imaging can read and write XMP metadata for several raster and vector formats (e.g., EPS, PDF, PNG), but it does not currently expose an API for adding or modifying XMP metadata directly in CorelDRAW (.cdr) files.

Why it happens
The XMP‑metadata features in Aspose.Imaging are implemented in format‑specific classes such as PsDocument for EPS. The library’s public API does not contain a CdrDocument, CorelDrawDocument, or a generic XmpMetadata member that works with .cdr files. Consequently, the SDK cannot write XMP data to CorelDRAW documents at this time.

What to do next

  1. Verify format support
  • Check the Aspose.Imaging documentation or the “Supported File Formats” list to see whether CorelDRAW (.cdr) is listed as a readable/writable format.
  • If the format appears only for raster conversion (e.g., to PNG) and not for metadata operations, the XMP write capability is unavailable.
  1. Run a quick compile‑time test (optional)
// .NET example – attempt to load a CDR file
using Aspose.Imaging;

string cdrPath = @"C:\sample.cdr";
using (var image = Image.Load(cdrPath))
{
// No XmpMetadata property exists for CDR, so this code will not compile.
}
  • A compilation error confirming the missing XmpMetadata member validates that the feature is not supported.
  1. Consider practical work‑arounds
  • Convert to a format that supports XMP (e.g., EPS, PDF, PNG) using Aspose.Imaging, add the XMP metadata there, and keep the converted file if it fits your workflow.
  • Use a dedicated CorelDRAW SDK or another third‑party library that explicitly provides XMP manipulation for .cdr files.
  • Store metadata externally (e.g., side‑car XMP files) and associate them with the CorelDRAW document in your application logic.
  1. Track future support
  • Monitor Aspose.Imaging release notes and the product roadmap for any announcement of XMP‑metadata support for CorelDRAW files.
  • If this capability is essential for your project, you can submit a feature‑request through the official Aspose feedback channel so the product team is aware of the demand.
  1. Internal follow‑up
  • Document the limitation in your project’s technical specifications.
  • If the requirement changes (e.g., a newer SDK version adds the needed API), revisit the implementation using the appropriate Aspose.Imaging classes.

:warning: I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.