The following tables provide implementation details about how Aspose.Words saves a document in the PDF format.
Any document loaded into Aspose.Words can be converted to PDF that conforms to the PDF 1.5 or PDF/A-1b specification. Support for PDF/A-1a specification is planned.
Aspose.Words provides one of the highest fidelity Word document to PDF conversion around. Many document features are exported to PDF exactly as how they appear in the original document.
You can also sign a PDF document and specify permissions such as allowing copying, modification or printing of the PDF document.
Aspose.Words also provides save options to control how PDF generation is handled. The following is some examples of such options:
· Export bookmarks or heading styles to the document outline (navigation pane) in PDF.
· Specify the page range only to export.
· Specify if the PDF uses core or windows fonts (can be used to decrease PDF size).
· Set JPEG quality used during rendering.
· Specifiying text compression used
Both TrueType and OpenFont font formats are supported and can be subsetted during rendering to PDF.
See the following links in the documentation for further information:
· PdfSaveOptions
· PdfSaveOptions.Compliance
Feature |
Supported |
Comment |
See Also |
Attached Template |
N/A |
|
|
Built-In Properties |
Yes |
Built-in properties such as word and character count are updated using Aspose.Words but are not updated automatically on save. Instead you need to explictly update these properties using the appropriate Document member. We will add automatic update of these properties in a future version. Title, Author, Subject, Keywords is output to PDF. |
· Document.UpdateWordCount |
Custom Properties |
Yes |
There is an option to export custom properties as metadata to PDF. The metadata exported to PDF in this way is given the namespace "custprops" e.g custprops:MyProperty. |
· PdfSaveOptions.ExportCustomPropertiesAsMetadata |
Custom Payload Part |
N/A |
|
|
Custom XML Data Storage |
N/A |
|
|
Digital Signature |
Yes |
Non-visible digital signature is supported. There are plans to support visible signatures in a future verison of Aspose.Words. |
· PdfSaveOptions.DigitalSignatureDetails |
Embedded Package |
N/A |
Exported as a plain image. |
|
Encryption |
Yes |
Creation of a PDF document with encryption and permissions is supported. RC4 encryption with key-length of 40 and 128 bit is supported. AES Encryption is not yet supported but will be planned for a later release. |
· PdfSaveOptions.EncryptionDetails |
Font Table |
Yes |
|
|
Glossary Document/Quick Parts/Auto Text |
N/A |
|
|
Hyphenation |
Planned |
Paragraphs that require hyphenation are wrapped to the next line instead. |
|
Key Map Customizations |
N/A |
|
|
Mail Merge Recipient Data |
N/A |
|
|
Office Math |
Planned |
It is planned to convert Office Math to a regular image before rendering. |
|
Themes |
Yes |
|
|
Toolbar Customizations |
N/A |
|
|
Variables |
N/A |
|
|
VBA Project (Macro) |
N/A |
|
|
VBA Project Digital Signature |
N/A |
|
|
Background |
Yes |
|
|
Thumbnail |
N/A |
Most rendered formats display thumbnails, however they are generated by the host application on open and not stored with the document. |
|
Feature |
Supported |
Comment |
See Also |
Embedding Fonts |
Yes |
There is an option to embed full fonts or a subset only of the glyphs used in the document to PDF. There are plans to introduce an option to control whether fonts are embedded at alll. TrueType and PostScript fonts can be subsetted. PostScript fonts are embedded fully. Fonts that are embedded in the original DOCX are used during rendering and exported to PDF. |
· PdfSaveOptions.EmbedFullFonts · PdfSaveOptions.UseCoreFonts · PdfSaveOptions.UseWindowsFont |
Embed Only Non-Standard Fonts |
Yes |
There is an option to embed only non-standard fonts. |
· PdfSaveOptions.EmbedStandardWindowsFonts |
Feature |
Supported |
Comment |
See Also |
Bibliography |
Yes |
Bibliography text is saved to PDF as normal text. |
|
Sources/Citations |
Yes |
Bibliography sources are not saved to PDF |
|
Citation Style |
N/A |
|
|
Feature |
Supported |
Comment |
See Also |
Allow Only Comments |
N/A |
|
|
Allow Only Form Fields |
N/A |
|
|
Allow Only Revisions |
N/A |
|
|
Limit Formatting to Selection of Styles |
N/A |
|
|
Protection Password (Legacy) |
N/A |
|
|
Protection Password (OOXML) |
N/A |
|
|
Protected Sections |
N/A |
|
|
Protection Ranges |
N/A |
|
|
Read Only |
N/A |
|
|
Feature |
Supported |
Comment |
See Also |
Asian Typography Settings |
N/A |
|
|
Compatibility Options |
N/A |
Compatibility Options can influence how the document content is appears. These properties are not supported upon rendering to PDF. |
|
Endnote Options |
N/A |
|
|
Footnote Options |
N/A |
|
|
Mail Merge Settings |
N/A |
|
|
Print Settings |
N/A |
|
|
Show/Hide Settings |
N/A |
|
|
View Settings |
Planned |
There are plans to export view settings to PDF that are applicable to the format, such as default zoom amount. |
|
Web Settings |
N/A |
|
|
XML Settings |
N/A |
|
|
Paragraphs with Heading styles can be exported to PDF so they appear in the document outline. There is a save option to control this.
See the following link in the documentation for further information:
· PdfSaveOptions.HeadingsOutlineLevels
Feature |
Supported |
Comment |
See Also |
Paragraph Style |
Yes |
|
|
Alignment |
Yes |
The special "Thai Distributed" alignment is currently unsupported during rendering. Such alignment is rendered as left alignment. |
|
Right to Left Paragraph |
Planned |
Currently such paragraphs are rendered as left-to-right. |
|
Bullets and Numbers |
Yes |
|
|
Outline Level |
Yes |
|
|
Run Properties for the Paragraph Mark |
Yes |
|
|
Suppress Line Numbers |
Yes |
|
|
Suppress Hyphenation |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Left Indent |
Yes |
|
|
Right Indent |
Yes |
|
|
First Line Indent |
Yes |
|
|
Hanging Indent |
Yes |
|
|
Mirror Indents |
Yes |
|
|
Automatically Adjust Right Indent |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Space Before |
Yes |
|
|
Space After |
Yes |
|
|
Space Auto |
Yes |
|
|
Line Spacing |
Yes |
|
|
No Space between Conforming Paragraphs |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Widow/Orphan Control |
Yes |
|
|
Keep With Next |
Yes |
|
|
Keep Lines Together |
Yes |
|
|
Page Break Before |
Yes |
|
|
Floating content is generally supported well during rendering.
Currently floating shapes may not be properly positioned when anchor is nested in a cell, belongs to a wrapped line or belongs to a paragraph with first/hanging indents, or to a 2nd column on the page, and other advanced layouts. This may cause some content to overlap in the rendered output.
We are working to improve this with each release.
Feature |
Supported |
Comment |
See Also |
Text Frames |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Absolute Position |
Yes |
|
|
Relative Position |
Planned |
|
|
Alignment: Left, Center, Right, Decimal, Bar |
Yes |
|
|
Leader |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Drop Caps |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Border Sides |
Yes |
|
|
Shadow |
Yes |
|
|
3D Frame |
Yes |
|
|
Style |
Yes |
|
|
Color |
Yes |
|
|
Width |
Yes |
|
|
Distance from Text |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Shading |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Use Asian Rules for Controlling First and Last Characters |
Planned |
|
|
Allow Latin Text to Wrap in the Middle of a Word |
Planned |
|
|
Allow Hanging Punctuation |
Planned |
|
|
Allow Punctuation at Start of a Line to Compress |
Planned |
|
|
Automatically Adjust Space between Asian and Latin Text |
Yes |
|
|
Automatically Adjust Space between Asian Text and Numbers |
Yes |
|
|
Text Vertical Alignment |
Planned |
|
|
Text in different languages is fully supported and can be rendered to formats such as PDF and image with high fidelity.
See the following link in the documentation for further information:
· PdfSaveOptions.TextCompression
Feature |
Supported |
Comment |
See Also |
Western Languages |
Yes |
|
|
East European Languages |
Yes |
|
|
East Asian Languages |
Yes |
|
|
Right to Left Languages |
Planned |
|
|
Carriage Return (not a Paragraph Break) |
Yes |
|
|
Non Breaking Space |
Yes |
|
|
Non Breaking Hyphen |
Yes |
|
|
Soft Hyphen |
Yes |
This type of hyphen is referred to as an "Optional Hyphen" in Microsoft Word documents. |
|
Symbol |
Yes |
|
|
Tab |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Line Break |
Yes |
|
|
Line Break Clear Type |
Yes |
|
|
Page Break |
Yes |
|
|
Column Break |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Character Style |
Yes |
|
|
Color |
Yes |
|
|
East Asian Typography |
Yes |
Not all features are supported. |
|
Highlight Color |
Yes |
|
|
Language |
Yes |
|
|
Do not Check Spelling or Grammar |
N/A |
|
|
Border |
Yes |
|
|
Shading |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Font |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Underline Type |
Yes |
|
|
Underline Color |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Animated Effect |
N/A |
|
|
Double Strikethrough |
Yes |
|
|
Strikethrough |
Yes |
|
|
Subscript/Superscript |
Yes |
|
|
Shadow |
Yes |
|
|
Outline |
Yes |
|
|
Emboss |
Yes |
|
|
Imprint (Engrave) |
Yes |
|
|
Small Caps |
Yes |
|
|
All Caps |
Yes |
|
|
Hidden Text |
Yes |
|
|
Special Hidden |
Yes |
|
|
Web Hidden |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Scale |
Yes |
|
|
Expanded/Compressed |
Yes |
|
|
Vertical Position |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Nested Tables |
Yes |
|
|
Right To Left Tables |
Planned |
Currently exported as left-to-right. |
|
Table Style |
Yes |
When a table style is present, it is converted to direct formatting on save so all formatting is still preserved. |
|
Conditional Formatting Style |
Yes |
|
|
Table Alignment |
Yes |
|
|
Table Indent |
Yes |
|
|
Allow AutoFit |
Yes |
|
|
Default Cell Margins |
Yes |
|
|
Default Cell Spacing |
Yes |
|
|
Preferred Table Width |
Yes |
|
|
Table Shading |
Yes |
|
|
Hidden |
Planned |
Hidden table or row is currently exported as visible to rendered format. |
|
Aspose.Words provides great support for the rendering of floating tables.
Currently floating shapes may not be properly positioned when anchor is nested in a cell, belongs to a wrapped line or belongs to a paragraph with first/hanging indents, or to a 2nd column on the page, and other advanced layouts. This may cause some content to overlap in the rendered output.
We are working to improve this with each release.
Feature |
Supported |
Comment |
See Also |
Horizontal Position |
Yes |
|
|
Horizontal Position Relative To |
Yes |
|
|
Vertical Position |
Yes |
|
|
Vertical Position Relative To |
Yes |
|
|
Distance from Text |
Yes |
|
|
Move with Text |
Yes |
|
|
Allow Overlap Floating Tables |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Table Borders |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Allow Break Across Pages |
Yes |
|
|
Repeat as Header Row |
Yes |
|
|
Height |
Yes |
|
|
Height Rule |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Cell Margins |
Yes |
|
|
Borders |
Yes |
|
|
Shading |
Yes |
|
|
Wrap Text |
Yes |
|
|
Fit Text |
Yes |
|
|
Preferred Width |
Yes |
|
|
Merged Horizontally |
Yes |
|
|
Merged Vertically |
Yes |
|
|
Vertical Alignment |
Yes |
|
|
Text Direction |
Yes |
|
|
When converting to a document format that doesn't support custom markup features, the markup is stripped but content is preserved. The non-Microsoft Word document formats do not support custom markup and only text is exported.
Feature |
Supported |
Comment |
See Also |
CustomXML |
N/A |
|
|
Currently Content Controls linked to Custom XML Data Storage are not supported during export. The default value of the tag is exported instead. This may make the output appear different to how the content control appears in Microsoft Word.
There are plans to export structure document tags to PDF for enhanced accessibility. The controls are exported as HTML which can be read and interpreted by screen readers
Feature |
Supported |
Comment |
See Also |
Content Controls (Structured Document Tags) |
Planned |
|
|
Feature |
Supported |
Comment |
See Also |
Smart Tag Properties |
N/A |
|
|
Feature |
Supported |
Comment |
See Also |
Different First Page |
Yes |
|
|
Different Even and Odd Pages |
Yes |
|
|
Continue from Previous Section |
Yes |
|
|
See the following links in the documentation for further information:
· Section.SectionStart
· DocumentBuilder.InsertBreak
Feature |
Supported |
Comment |
See Also |
Continuous |
Yes |
|
|
Even Page |
Yes |
|
|
Odd Page |
Yes |
|
|
Next Column |
Yes |
|
|
Next Page |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Text Columns |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Page Margins |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Number Format |
Yes |
|
|
Starting Number |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Right to Left Section |
Planned |
|
|
Line Numbering |
Yes |
|
|
Paper Source |
N/A |
|
|
Paper Size |
Yes |
|
|
Orientation |
Yes |
|
|
Protection |
N/A |
|
|
Text Direction |
Yes |
|
|
Vertical Alignment |
Yes |
|
|
Asian Document Grid |
Planned |
|
|
Feature |
Supported |
Comment |
See Also |
Chapter Numbering |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Page Border |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Paragraph Style |
Yes |
|
|
Character Style |
Yes |
|
|
List Style |
Yes |
|
|
Table Style |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Aliases |
Yes |
|
|
Based On |
Yes |
|
|
Built-in Styles |
Yes |
|
|
Custom Styles |
Yes |
|
|
Style Name |
Yes |
|
|
Next Style |
Yes |
|
|
Paragraph Properties |
Yes |
|
|
Run Properties |
Yes |
|
|
Bullets and Numbering |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Paragraph Properties |
Yes |
|
|
Run Properties |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Apply Formatting to |
Yes |
|
|
Table Properties |
Yes |
|
|
Banding |
Yes |
|
|
Paragraph Properties |
Yes |
|
|
Run Properties |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Single Level |
Yes |
|
|
Multi Level |
Yes |
|
|
Name |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Label Alignment |
Yes |
|
|
Picture Bullet |
Yes |
|
|
Restart Level |
Yes |
|
|
Bullet Character |
Yes |
|
|
Label/Format String |
Yes |
|
|
Number Format |
Yes |
|
|
Paragraph Properties |
Yes |
|
|
Font Properties |
Yes |
|
|
Linked Paragraph Style |
Yes |
|
|
Starting Value |
Yes |
|
|
Text After |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Reference Mark |
Yes |
|
|
Custom Reference Mark |
Yes |
|
|
Custom Separator |
Yes |
|
|
Continuation Separator Mark |
Planned |
|
|
Document Wide Properties |
Yes |
|
|
Section Wide Properties |
Yes |
|
|
Number Format |
Yes |
|
|
Restart Location |
Yes |
|
|
Starting Value |
Yes |
|
|
Placement |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Reference Mark |
Yes |
|
|
Custom Reference Mark |
Yes |
|
|
Custom Separator |
Yes |
|
|
Continuation Separator Mark |
Planned |
|
|
Document Wide Properties |
Planned |
|
|
Section Wide Properties |
Planned |
|
|
Number Format |
Planned |
|
|
Restart Location |
Planned |
|
|
Starting Value |
Planned |
|
|
Placement |
Planned |
|
|
All Word documents and most other formats that Aspose.Words export to only allow bookmarks with unqiue names, that is, no two bookmarks are allowed the exact same name.
If two bookmarks are given the same name in the model then no errors will occur. During export to any format the duplicate bookmarks are removed silently. The first bookmark visited in the model is the one that is retained, any other bookmarks are removed,
Bookmarks are exported to PDF and can be made to appear the document outline by using the appropriate save option.
See the following link in the documentation for further information:
· PdfSaveOptions.BookmarksOutlineLevel
Feature |
Supported |
Comment |
See Also |
Bookmark Start |
Yes |
|
|
Bookmark End |
Yes |
|
|
Bookmark Name |
Yes |
|
|
Bookmark Table Columns |
N/A |
|
|
Comments are exported to PDF.
In version 1.0 of comments rendering long or many comments are not truncated in PDF output.
Feature |
Supported |
Comment |
See Also |
Comment |
Yes |
|
|
Comment Range |
Yes |
|
|
Author |
Yes |
|
|
Date |
Yes |
|
|
Initial |
Yes |
|
|
You may need to accept tracked changes before saving to different formats or else the deleted revisions will still show up in the output document.
Tracked changes are currently not exported to PDF in the way they appear in Microsoft Word. This functionality will be included in a future version of Aspose.Words. At the moment any tracked changes are exported to PDF as plain content and thefore may affect the apperance of the document. For this reason you may need to accept all revisions before rendering.
In a future version there will be an option to render the document in any level of "mark up" e.g Final with Markup, Final (without markup) etc.
For now rendering simple insertion, change or deletion revisions can be simulated by applying appropriate run formatting on these revisions before rendering.
See the following link in the documentation for further information:
· Document.AcceptAllRevisions
Feature |
Supported |
Comment |
See Also |
On/Off State |
Planned |
|
|
Table Cell Deletion |
Planned |
|
|
Table Cell Insertion |
Planned |
|
|
Cell Merge or Split |
Planned |
|
|
Run Deletion |
Planned |
|
|
Run Insertion |
Planned |
|
|
Paragraph Deletion |
Planned |
|
|
Paragraph Insertion |
Planned |
|
|
Table Row Deletion |
Planned |
|
|
Table Row Insertion |
Planned |
|
|
Numbering Insertion |
Planned |
|
|
Numbering Change |
Planned |
|
|
Moves |
Planned |
|
|
Paragraph Properties Change |
Planned |
|
|
Run Properties Change |
Planned |
|
|
Section Properties Change |
Planned |
|
|
Table Properties Change |
Planned |
|
|
Cell Properties Change |
Planned |
|
|
Row Properties Change |
Planned |
|
|
RSIDs Session Identifiers |
Planned |
RSID ids on revisions are preserved even when converting to different formats. |
|
Fields are supported in the model. To check if these fields can be updated check the import section.
Even if a field can be updated, most fields are exported if they are up-to-date by MS Word. i.e if you import a doucment and export it with a field as it is then it will appear properly in the output format.
Fields with custom field codes (a field code modified to represent something different than a normal field) are retained as they are when converting to other Word document formats. These fields are lost when exporting to ODT.
When saving to rendered formats such as PDF, XPS or image some fields may be automatically updated as a part of page layout.
See the following link in the documentation for further information:
· Document.UpdateFields.
Feature |
Supported |
Comment |
See Also |
Field Codes |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
CreateDate |
Yes |
|
|
Date |
Yes |
|
|
EditTime |
Yes |
|
|
PrintDate |
Yes |
|
|
SaveDate |
Yes |
|
|
Time |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Compare |
Yes |
|
|
DocVariable |
Yes |
|
|
GoToButton |
Yes |
|
|
If |
Yes |
|
|
MacroButton |
Yes |
|
|
|
N/A |
|
|
Fields such as FileName or FileSize are not automatically updated on save. However they can be updated explictly by calling Document.UpdateFields.
Feature |
Supported |
Comment |
See Also |
Author |
Yes |
|
|
Comments |
Yes |
|
|
DocProperty |
Yes |
|
|
FileName |
Yes |
|
|
FileSize |
Yes |
|
|
Info |
Yes |
|
|
Keywords |
Yes |
|
|
LastSavedBy |
Yes |
|
|
NumChars |
Yes |
|
|
NumPages |
Yes |
|
|
NumWords |
Yes |
|
|
Subject |
Yes |
|
|
Template |
Yes |
|
|
Title |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Formula |
Yes |
|
|
Advance |
Planned |
The effects of the advance field do not appear in the rendered output. There are plans to support this field during rendering. |
|
Eq |
Planned |
Some simple equation fields may render correctly. Others may appear distorted in the rendered output. |
|
Symbol |
Yes |
|
|
There is a save option to control if form fields are exported as proper form fields in PDF output or as plain text.
See the following link in the documentation for further information:
· PdfSaveOptions.PreserveFormFields
Feature |
Supported |
Comment |
See Also |
TextInput |
Yes |
|
|
CheckBox |
Yes |
|
|
DropDown |
Yes |
|
|
Calc On Exit |
N/A |
|
|
Checked |
Yes |
|
|
Default Value |
Yes |
|
|
Enabled |
Yes |
|
|
Entry and Exit Macro |
N/A |
|
|
Name |
Yes |
|
|
Help Text |
N/A |
|
|
Status Text |
N/A |
|
|
Max Length |
Yes |
|
|
Check Box Size |
Yes |
|
|
Text Input Type |
N/A |
|
|
Feature |
Supported |
Comment |
See Also |
Index |
Yes |
|
|
RD |
Yes |
|
|
TA |
N/A |
|
|
TC |
N/A |
|
|
TOA (Table of Authorities) |
Yes |
|
|
TOC (Table of Contents) |
Yes |
The \h switch on TOC can be used to export the TOC as hyperlinked to PDF. |
|
XE |
N/A |
|
|
Feature |
Supported |
Comment |
See Also |
AutoText |
Yes |
|
|
AutoTextList |
N/A |
|
|
Bibliography |
Yes |
|
|
Citation |
N/A |
|
|
Hyperlink |
Yes |
Output to PDF as a clickable hyperlink. |
|
IncludePicture |
Yes |
|
|
IncludeText |
Yes |
|
|
Link |
Yes |
|
|
NoteRef |
Yes |
Exported as clickable link. |
|
PageRef |
Yes |
Hyperlinked PageRef field is exported as plain text and not as a clickable hyperlink in output PDF. |
|
Quote |
Yes |
|
|
Ref |
Yes |
Exported as clickable link. |
|
StyleRef |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
AddressBlock |
Yes |
|
|
Ask |
Yes |
|
|
Compare |
Yes |
|
|
Database |
Yes |
|
|
Fill-in |
Yes |
|
|
GreetingLine |
Yes |
|
|
If |
Yes |
|
|
MergeField |
Yes |
|
|
MergeRec |
Yes |
|
|
MergeSeq |
Yes |
|
|
Next |
Yes |
|
|
NextIf |
Yes |
|
|
Set |
Yes |
|
|
SkipIf |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
AutoNum |
Planned |
|
|
AutoNumLgl |
Planned |
|
|
AutoNumOut |
Planned |
|
|
BarCode |
Planned |
Note that this only refers to the BarCode field structure. Commonly barcodes are actually represented in Microsoft Word document as text using a special barcode font or image. These are fully supported during export to all formats. |
|
ListNum |
Planned |
|
|
Page |
Yes |
|
|
RevNum |
Yes |
|
|
Section |
Yes |
|
|
SectionPages |
Yes |
|
|
Seq |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
UserAddress |
Yes |
|
|
UserInitials |
Yes |
|
|
UserName |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Text |
Yes |
|
|
Hyperlinked Shape or Image |
Yes |
Hyperlink is only exported on an image and not a shape. |
|
Hyperlink across Multiple Paragraphs |
Yes |
|
|
Hyperlink to a Local Bookmark |
Yes |
|
|
Hyperlink to an External Resource |
Yes |
|
|
Screen Tip |
N/A |
|
|
Target Frame |
N/A |
|
|
Feature |
Supported |
Comment |
See Also |
Date and Time Formatting |
Yes |
|
|
Numbering Formatting |
Yes |
|
|
General Formatting |
Yes |
|
|
All images are exported as the same format that they were originally loaded as.
Feature |
Supported |
Comment |
See Also |
PNG |
Yes |
|
|
JPG |
Yes |
|
|
WMF |
Yes |
There is a save option to control exporting metafiles to PDF as vector images or to rasterize them first. |
· PdfSaveOptions.MetafileRenderingMode |
EMF |
Yes |
|
|
EMF+ |
Yes |
|
|
BMP |
Yes |
|
|
GIF |
Yes |
|
|
TIFF |
Yes |
|
|
Borders |
Yes |
|
|
Cropping |
Yes |
|
|
Alternative text |
Planned |
It is planned to export alternative text to PDF if the input image cannot be located during rendering. |
|
Feature |
Supported |
Comment |
See Also |
Brightness |
Yes |
|
|
Contrast |
Yes |
|
|
Recolor |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Text Direction |
Yes |
|
|
Linked Textboxes |
Planned |
Linked text boxes are currently unsupported when rendering to PDF. |
|
Internal Margins |
Yes |
|
|
Vertical Alignment |
Yes |
|
|
Resize To Fit Text |
Yes |
|
|
Text in Other Shapes |
Yes |
|
|
OLE Objects represent embedded content in a Microsoft Word document, such as an embedded Excel or Powerpoint document. The OLE object is dynamic and can be edited or updated through Microsoft Word.
OLE objects are fully preserved when converting within different Word document formats.
OLE objects are saved as images.
Feature |
Supported |
Comment |
See Also |
Linked |
N/A |
|
|
Embedded |
N/A |
|
|
Draw Aspect |
N/A |
|
|
Auto Update |
N/A |
|
|
Lock |
N/A |
|
|
Ole Object Data |
N/A |
|
|
Ole Object Picture |
Yes |
|
|
Source Range |
N/A |
|
|
Output as a regular image.
Feature |
Supported |
Comment |
See Also |
Persistent Properties Storage |
N/A |
|
|
Feature |
Supported |
Comment |
See Also |
Lines |
Yes |
|
|
Basic Shapes |
Yes |
|
|
Block Arrows |
Yes |
|
|
Flowcharts |
Yes |
|
|
Callouts |
Yes |
|
|
Stars and Banners |
Yes |
|
|
Group Shape |
Yes |
|
|
Drawing Canvas |
Yes |
|
|
Signature Line |
N/A |
PDF does not have any signature line feature. A signature line is exported as a regular image. Only the original part of the signature is exported, any signed component of the signature is not rendered. |
|
Ink Annotation |
Yes |
Ink Annotations are exported to all formats as regular images. |
|
Clip Art |
Yes |
|
|
Diagrams (VML) |
Yes |
VML graphic format is normally used in pre-OOXML formats such as DOC or RTF. |
|
SmartArt (VML) |
Yes |
|
|
Charts (VML) |
Yes |
|
|
Shape Customizations |
Yes |
|
|
Hyperlink on Shape |
Yes |
|
|
Watermark |
Yes |
A watermark in a Microsoft Word document is actually a text shape or image centered in the middle of the page but in the header or footer. This allows the watermark to appear behind all content and as faded. |
|
DrawingML is only preserved in round-trip back to DOCX format.
There are plans to export DrawingML as regular shape/image to other formats. At the moment DrawingML objects are lost when converting to other formats.
Support for DrawingML is improving with every new release.
Feature |
Supported |
Comment |
See Also |
Images/Shapes |
Yes |
Simple DrawingML images are converted to regular images upon export to non-OOXML formats. |
|
Diagrams |
Planned |
|
|
SmartArt |
Planned |
|
|
Charts |
Planned |
|
|
Feature |
Supported |
Comment |
See Also |
Styles |
Yes |
|
|
Outline |
Yes |
|
|
Fill |
Yes |
|
|
3D Properties |
Planned |
|
|
Text Spacing |
Planned |
|
|
Vertical Text |
Planned |
Exported as rotated text. |
|
Even Height |
Planned |
|
|
Align and Justify Text |
Planned |
|
|
WordArt Shape |
Yes |
Only some shapes are supported. |
|
Feature |
Supported |
Comment |
See Also |
Width |
Yes |
|
|
Height |
Yes |
|
|
Color |
Yes |
|
|
Alignment |
Yes |
|
|
Hyperlink |
Yes |
Hyperlink preserved on export to PDF. |
|
Image |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Inline |
Yes |
|
|
Floating |
Yes |
Floating content is exported well during rendering. Currently floating shapes may not be properly positioned when anchor is nested in a cell, belongs to a wrapped line or belongs to a paragraph with first/hanging indents, or to a 2nd column on the page, and other advanced layouts. This may cause some content to overlap in the rendered output. This is being worked on and improvements are included with each release. |
|
Wrap Type |
Yes |
Text wrapping around images and shapes is supported in all formats. The following wrap types are fully supported upon rendering: · Square · Top and Bottom · Behind Text · Infront of Text · Inline with Text The following wrap types are currently unsupported: · Tight · Through These wrap types are rare and most of the time do not have any visible difference when compared to Square wrapping. The only time you really see differences if text is wrapped around complex objects e.g a Star shaped AutoShape. These two wrap types will be supported in a future version. Currently they are exported as "Square" wrapping which produces very close output. |
|
Wrap Sides |
Planned |
Both sides is the only Wrap Sides option supported at the moment. Other types such as Left Only, Right Only, Largest Only are currently unsupported as are exported as "Both sides" wrapping. These wrap types will be supported in a future version. |
|
Distance from Text |
Yes |
|
|
Z-Order |
Yes |
|
|
Polygon Wrap Points |
Planned |
Custom wrap points are lost on export. This will be implemented in a future version. Exported as "Square" wrap type. |
|
Rotation |
Yes |
|
|
Flip |
Yes |
|
|
Horizontal Alignment |
Yes |
|
|
Horizontal Position Relative To |
Yes |
|
|
Vertical Alignment |
Yes |
|
|
Vertical Position Relative To |
Yes |
|
|
Anchor Lock |
N/A |
|
|
Allow Overlap |
Yes |
|
|
Layout in Table Cell |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Width and Height |
Yes |
|
|
Scale |
Yes |
A scaled object is normally exported with scaling applied to the Shape size and the Scale property reset to 100%. |
|
Relative Size |
Yes |
|
|
Lock Aspect Ratio |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
No Fill |
Yes |
|
|
Solid Fill |
Yes |
|
|
Gradient Fill |
Yes |
|
|
Pattern Fill |
Yes |
|
|
Picture or Texture Fill |
Yes |
|
|
Feature |
Supported |
Comment |
See Also |
Line Color |
Yes |
|
|
Line Fill |
Yes |
|
|
Line Width |
Yes |
|
|
Compound Type |
Yes |
|
|
Dash Type |
Yes |
|
|
Cap Type |
Yes |
|
|
Join Type |
Yes |
|
|
Arrow Settings |
Yes |
|
|
Shadow on shape is currently lost upon rendering to PDF.
Feature |
Supported |
Comment |
See Also |
Shadow |
Planned |
|
|
3D properties are currently lost upon rendering.
Feature |
Supported |
Comment |
See Also |
3D Properties |
Planned |
|
|