GroupDocs.Total for .NET 26.4 Release Notes

There are 5 features, improvements, and bug fixes in this release.

This release concentrates on stabilizing and correcting format handling across the suite—addressing EPSF, DXF, and MSG processing errors in Viewer, Conversion, and Metadata to ensure reliable rendering, conversion, and preservation of message properties.

Full list of changes in this release

TOTALNET-350: [Metadata] MSG File Properties and Transport Message Headers Change After Open/Save with GroupDocs.Metadata

The issue where Sender Email property was changed during processing with GroupDocs.Metadata is now fixed. The following code keeps Sender Email as it is in source MSG file:

using(Metadata metadata = new Metadata("test.msg"))
{
  MsgRootPackage root = metadata.GetRootPackage<MsgRootPackage>();
  MsgPackage msg = root.EmailPackage;
  metadata.Save();
}

TOTALNET-352: [Conversion] Special characters not working in certain MSG in .NET

This issue is now fixed, before some special characters displayed as boxes in the output PDF files when converting from MSG:

var loadOptions = new EmailLoadOptions
{
    ConvertOwned = false
};
var convertOptions = new PdfConvertOptions();

FluentConverter.Load("source.msg").WithOptions(loadOptions)
    .ConvertTo("converted.pdf")
    .WithOptions(convertOptions)
    .Convert();

TOTALNET-366: [Viewer] EPSF format support is limited. An error occurred while parsing the EPSF file content

The root cause. The file was exported by sK1 (open‑source vector tool, listed as %%Creator: Adobe Illustrator exported by sK1), and the exporter has a bug: it emitted 78 lines of unfilled C‑style format strings:

[%d %d %d %d ] 0 d

instead of real dash‑pattern arrays like [3 2 1 2] 0 d. In PostScript, % starts a line comment, so to a real PostScript / EPSF parser this line tokenizes as:

• [ — open an array
• %d %d %d %d ] 0 d — comment, consumed to end of line

The ] is inside the comment, so the array is never closed. Each of the 78 broken lines opens an array that’s never closed, and parsing hits EOF with arrays still on the stack → exactly the GroupDocs error: “end of content before end of array character.” (A naive bracket count looks balanced — 82/82 — because that counter doesn’t honor %-comments.) These are the only %d occurrences in the file (312 = 78 × 4), so this is the sole defect.

The fix: we replace each [%d %d %d %d ] 0 d with a valid dash array. The original dash values are lost (sK1 never wrote them), so we can’t recover them.

TOTALNET-367: [Conversion] No font was found exception when converting MSG to PDF

The root cause of the issue is that we depend on some .NET Standard assemblies that we can’t replace at the moment, while we looking for a replacement the users should set biding redirects in their .NET Framework applications in case they do not have auto binding redirects setting enabled. Binding redirects for added for package.json consumers and list of binding redirects also added to README.md of the .NET Framework package.

Products included in this release

How to Download

The packages can be downloaded from NuGet or via direct download from this website.

Additional Resources

• Product Overview
• System Requirements
• Technical Support

Feedback

We value your feedback! If you have any questions, issues, or suggestions, feel free to reach out to us through our Free Support Forum. Our team will be happy to assist you and answer any questions you may have.