Syncfusion Excel Export Corrupts Accented Characters in VBA Macros

[Aitbouhou Adam]

Hello

I’m using Syncfusion Excel to generate Excel files from a base template.
This template file contains macros with text that includes accented characters (such as é, è, ê, etc.).

The issue is that after generating the Excel file with Syncfusion, the text inside the macros is not properly formatted—accented characters appear incorrectly or are distorted.

How can I fix this issue and ensure that accented characters in macros are preserved correctly when generating the file with Syncfusion?

Thank you rery much 

Attachment: syncfusion_30e13a2a.zip

[Karthika Santhana Krishnan]

Hi Aitbouhou,

We have checked the attachments.

The accented characters are changed according to the screenshot references.

These issues occur when the text encoding used in the Macro code differs from the input template Excel document.

But the shared Excel document is generated from XlsIO.

We need the input template document used for generating the Excel document to validate further from our end.

Regards,

Karthika S.

[Aitbouhou Adam]

Hello 

This my tempalte 

thanks

Attachment: Base_Suivi_Pro_KT_(2)_9ffcd150.zip

[Karthika Santhana Krishnan]

Hi Aitbouhou,

 

The reported issue has been resolved with the latest Nuget. 

 

We have attached a sample for your reference. 

 

If the issue still persists, please feel free to contact us.

 

Regards,

Karthika S.

Attachment: VbaMacroIssue_8ec62e8f.zip

[Aitbouhou Adam]

Hello 

I used your provided example, but it didn't work. It still produces incorrect characters, even though I'm using .NET version 7.

Thank you for your replay 

Attachment: OutputX2_6115e70c.zip

[Karthika Santhana Krishnan]

Hi Aitbouhou,

 

We are currently validating the issue on our end.

 

We will share the validation details on July 16, 2025.

 

Regards,

Karthika S.

[Karthika Santhana Krishnan]

Hi Aitbouhou,

 

.NET 7 is no longer supported in our source and has been removed. We recommend upgrading your project to .NET 8 or .NET 9. This should resolve the issue. Please let us know if you need any further clarification.

 

Regards,

Karthika S.