GroupDocs.Editor for .NET 20.6 Release Notes

GroupDocs.Editor for .NET version 21.6 presents several small but useful new features, several improvements and a lot of different bugfixes; all of these are described below. As in most of previous releases, these new features, which touch a public API, do not break a backward compatibility.

New features

Version 21.6 of GroupDocs.Editor contains three new features, which are described below

New Mime property in IDocumentFormat inheritors

Now a public interface Formats.IDocumentFormat contains a new public property: string Mime.

All implementing types — WordProcessingFormats, SpreadsheetFormats, PresentationFormats, TextualFormats, and EBookFormats, — also contain this property. With this property users can easily obtain a MIME-code for a particular format. This may be very useful in web-applications, where it is required to write a MIME-code to the response along with document content.

New XmlContent property in SvgImage class

SVG image is in fact a text document in XML format. Before this moment it was not possible to obtain this XML content, because a TextContent property of GroupDocs.Editor.HtmlCss.Resources.Images.Vector.SvgImage class returns a base64-encoded content. Now we introduced a new property XmlContent, which returns exactly a described XML content of a particular SVG image.

Extended conversion methods for all vector images

Starting from version 21.6 the VectorImageResourceBase class has a new abstract method void SaveToPng(System.IO.Stream outputPngContent), so now all implementing types (SvgImage, WmfImage and EmfImage) support conversion and saving to the PNG raster format.

Also MetaImageBase abstract class has a new abstract method void SaveToSvg(System.IO.Stream outputSvgContent), which allows to save WMF or EMF to SVG. This is very useful, because WMF and EMF formats are commonly used in WordProcessing documents, but are not supported by the browsers; on the other hand, only SVG is supported in the Web.


GroupDocs.Editor for .NET version 21.6 contains several important improvements, which may be divided onto two parts: improvements related to SVG and to the Presentation module.

Presentation module

Now Presentation module preserves and supports some basic text formatting features when converrting document to and from HTML. This includes:

  • Bold text
  • Italic text
  • Underline text
  • Subscript
  • Superscript
  • Strikethrough text

Now, if some slide contains such text formatting, this formatting will be present in HTML and then in the resultant Presentation document.

Better SVG support

First of all, starting from version 21.6, HTML/CSS module supports an SVG content, inlined inside HTML markup. This means that if given HTML document contains SVG images, which are inlined directly inside HTML using SVG elements, GroupDocs.Editor will correctly process such markup with SVG images without throwing an exception.

Another improvement is related to the serialization: now, when EditableDocument.GetEmbeddedHtml() method is invoked, all SVG files will not be encoded to the base64 and placed inside the values of “src” attributes of corresponding IMG elements, but rather will be stored in their native XML-compliant form, with SVG elements and so on.


GroupDocs.Editor version 21.3 contains big amount of bugfixes and performance improvements, which address different issues in different modules of GroupDocs.Editor, including WordProcessing, Spreadsheet, Presentation, and HTML processing.

Full List of Issues Covering all Changes in this Release

EDITORNET-2092Add new property with MIME code for all supportable document formatsNew feature
EDITORNET-2106Add ability to save SVG as PNG and improve public API in vector imagesNew feature
EDITORNET-2129Add new public property to obtain XML-content of SVG imageNew feature
EDITORNET-2093Preserve most common text formatting features during roundtrip in Presentation moduleImprovement
EDITORNET-2103SVG is not supported if is inlined into HTML markup as HTML elementImprovement
EDITORNET-2128Implement SVG inlining instead of base64 embeddingImprovement
EDITORNET-1989Images are not correctly transfered during conversion Markdown to DocxBug
EDITORNET-2066HTML-markup loose styles after file open and saving without changesBug
EDITORNET-2086OutOfMemoryException while converting specific Cells file to HTMLBug
EDITORNET-2089Presentation: convert html to presentation without stylesheetBug
EDITORNET-2090Exception while import Presentation with missing load optionsBug
EDITORNET-2094Exception with message Font name cannot be NULL, empty or whitespaces\r\nParameter name: fontName during call editor.Edit() for RTF-fileBug
EDITORNET-2096Unknown field is improperly processedBug
EDITORNET-2100Editor hang on PowerPoint filesBug
EDITORNET-2101Image is not JPEG exception in PresentationBug
EDITORNET-2127Fix bug in markup parserBug

Public API and Backward Incompatible Changes

New public methods:

  1. void VectorImageResourceBase.SaveToPng(System.IO.Stream outputPngContent)
  2. void SvgImage.SaveToPng(System.IO.Stream outputPngContent)
  3. void WmfImage.SaveToPng(System.IO.Stream outputPngContent)
  4. void EmfImage.SaveToPng(System.IO.Stream outputPngContent)
  5. void MetaImageBase.SaveToSvg(System.IO.Stream outputSvgContent)
  6. void WmfImage.SaveToSvg(System.IO.Stream outputSvgContent)
  7. void EmfImage.SaveToSvg(System.IO.Stream outputSvgContent)

New public properties:

  1. string Formats.IDocumentFormat.Mime
  2. string Formats.WordProcessingFormats.Mime
  3. string Formats.SpreadsheetFormats.Mime
  4. string Formats.PresentationFormats.Mime
  5. string Formats.TextualFormats.Mime
  6. string Formats.EBookFormats.Mime
  7. string SvgImage.XmlContent