Can’t find your file format?
We’re here to help! Please post a request on our Free Support Forum, and our team will assist you.
Supported Features Detail for Email File Formats
The following table provides information on those GroupDocs.Assembly features that are partially supported or not supported at all for email file formats.
Feature
MSG with RTF Body
MSG, EML, MHTML with HTML Body Created Using Microsoft Outlook or Microsoft Word
MSG, EML, EMLX, MHTML with HTML Body Created Outside Microsoft Outlook or Microsoft Word
MSG, EML, EMLX, MHTML with Plain Text Body
Building Charts Dynamically
Supported (outside loops and conditions)
Supported (outside loops and conditions)
Not supported
Not supported
Inserting Documents Dynamically
Supported
Supported
To be supported
Not supported
Inserting Images Dynamically
Supported
Supported
Supported
Not supported
Inserting Barcodes Dynamically
Supported
Supported
To be supported
Not supported
Supported Output File Formats Depending on Input File Formats
The following table shows which output file formats are supported by GroupDocs.Assembly depending on input file formats:
Input File Formats (from left to right) and Output File Formats (top down)
Documents can be inserted dynamically with a doc tag into Word Processing templates and email templates with HTML or RTF bodies only (see Supported Features Detail for Email File Formats for the email variants). In spreadsheet, presentation, HTML, Markdown and plain text templates, a doc tag fails with the following error:
Tag 'doc' is not supported for this template format. Documents can be inserted into Word Processing templates and email templates with HTML or RTF bodies only.
Encoding of Text and HTML Reports
A report built from a plain text or HTML template is written in the encoding of the template, determined in this order:
A byte order mark of the template.
An encoding declared in the template: <meta charset> in HTML, or an XML declaration.
The encoding of the template bytes. A template made of ASCII characters only gives a UTF-8 report without a byte order mark, so non-Latin data such as Привет is written correctly.
To get a report in an ANSI code page, declare that encoding in the template (<meta charset> in HTML), or save the template in that encoding with a non-ASCII character. An MHTML report saved from an ASCII-only template declares charset="utf-8".
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.
Ask AI
Ask anything about this page — the answer is based on its content.
Searching the docs and writing an answer…
Something went wrong while getting an answer. Please try again in a moment.