Slight top alignment for Excel emf

Aspose.Cells Product Family
1

Hi,

Aspose emf generated from excel has slightly top alignment can be seen in picture uploaded in zip file. When we use in built excel (Copy As Picture - as shown when printed) functionality the alignment is proper.

   Workbook workbook = new Workbook(@"English.xlsx");
    Worksheet worksheet = workbook.Worksheets[0];
    worksheet.PageSetup.PrintArea = "A1:B4";

    // Configure rendering options
    ImageOrPrintOptions imgOptions = new ImageOrPrintOptions
    {
        ImageType = ImageType.Emf,
        OnlyArea = false, // Render full sheet, not just used cells
        TextRenderingHint = TextRenderingHint.ClearTypeGridFit,
        Transparent = true,
        OnePagePerSheet = true // Prevents scaling issues
    };

    // Render sheet as image
    SheetRender sr = new SheetRender(worksheet, imgOptions);
    sr.ToImage(0, @"English.emf");

SlightTopAlignmentIssue.zip (84.9 KB)

Regards,

2

@ServerSide527,

Thanks for the template Excel file and screenshot.

I can notice the issue as you pointed out (via screenshot) using your sample file. There is slight top alignment for Excel spreadsheet to EMF conversion. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-58099

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

3

@ServerSide527 ,

We make some improvements, please check the attachment for preview and let us know your feedback.
output_pfrefix.zip (2.2 KB)

4

@ServerSide527
We are pleased to inform you that your issue CELLSNET-58099 has been resolved. The fix will be included in our upcoming release (Aspose.Cells for .NET 25.4) that we plan to release in the first half of April 2025. You will be notified when the next version is released.

5

The issues you have found earlier (filed as CELLSNET-58099) have been fixed in this update. This message was posted using Bugs notification tool by leoluo