This field allows performing a mail merge operations with labels representing different source items on the same page.

Add support for horizontal lines in documents.

In DOCX, such lines are defined using the legacy VML definitions:
The definitions above and the <hr/> HTML tag are currently not supported and skipped on import, leading to missing horizontal lines in the document.

Importing an image from HTML with URI as a source, which has applied only width or height and exporting it to PDF (which forces getting the image data so it can be drawn) leads to an incorrect value of 1 (a default value) for the dimension that is not specified.

The default table style is not respected from the style system for character or paragraph properties when exporting to PDF format. It looks only into the default paragraph style.

Steps to reproduce:
1. Create new Table style and set it as default.
2. Apply foreground themeable color with a value from the document theme. Like Accent1
3. Insert a table with some text in it.
4. Export to PDF.
Observed: The text inside the table is not with the color from the document theme.

When exporting to PDF a paragraph in a list, whose first run is longer than the line, the bullets are rendered with wrong baseline and not aligned with the text.

Importing a document containing a bookmark located in a  structured document tag (sdt) will lead to ArgumentNullException.

The properties applied to the paragraph marker are not respected when evaluating the style of the child elements. That leads to exporting the bullets in a list with their default settings when they are applied to the paragraph properties. The issue is reproducible when exporting to PDF and RTF.


Workaround, applicable when the style of all the bullets in the specific list is the same:

Change the style of the list level:
foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    if (paragraph.ListId > -1)
    {
        this.document.Lists.GetList(paragraph.ListId).Levels[paragraph.ListLevel].CharacterProperties.CopyPropertiesFrom(paragraph.Properties.ParagraphMarkerProperties);
    }
}

The control word (\~) is imported but the symbol is not parsed, therefore not included in the content.

Fix available in LIB Version 2017.2.814.

In scenarios when center and right tabs are used for aligning the paragraph content to both left and right the text content in the exported PDF is not positioned as expected.

When a paragraph doesn't have applied a style, the Normal style should be automatically applied. Currently, similar paragraph obtains its style from the parent.

This is reproducible when exporting to PDF and RTF.

Workaround: Check if there is a paragraph without style ID and if so, set it to Normal:

foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    var value = paragraph.StyleId;
    if (string.IsNullOrEmpty(value))
    {
        paragraph.StyleId = "Normal";
    }
}

Available in LIB Version 2017.2.731.

This setting should allow setting the content between the list level bullet and the paragraph text to some of the following options: "tab", "space", "nothing".

Form fields are the legacy way to insert an editable controls in a document (text boxes, checkboxes, dropdowns) by using the FORMTEXT, FORMCHECKBOX and FORMDROPDOWN fields.

Do not confuse with content controls (structured document tags) (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 ) and with ActiveX controls.

Add support for the All Caps and Small Caps properties of the runs. These properties are currently ommitted on import.

If HTML document is imported, and it contains image with invalid URL, then the image is imported with this URL in the document model. On subsequent export to Docx, the library tries to download the image data, which throws WebException. Instead, the image should be replaced with generic 'error' image.

Workaround: Manually test the image URL for correctness on HTML import, and replace the data:

        static void Main(string[] args)
        {
            HtmlFormatProvider htmlFormatProvider = new HtmlFormatProvider();
            htmlFormatProvider.ImportSettings.LoadFromUri += (sender, e) =>
            {
                if (!IsValid(e.Uri))
                {
                    e.SetData(File.ReadAllBytes("no-image.png"));
                }
            };
        }

        private static bool IsValid(string uri)
        {
            try
            {
                using (WebClient client = new WebClient())
                {
                    client.DownloadData(uri);
                }
            }
            catch (WebException)
            {
                return false;
            }

            return true;
        }

The same issue appears when exporting to PDF.

This property allows the user to set the transparency of the image watermark. In the XML, the property is written using the 'blacklevel' attribute of the image.

Importing shape with missing id attribute leads to NullReferenceException. 

 <v:shape type="#_x0000_t202" filled="false" stroked="false">

Import of Tables with border style needs improvements. Currently, it takes multiple seconds to import table with 100x6 cells no matter if the border style is defined globally or locally. This may be seen when importing the attached files "table with borders.html" and "table single border style.html". Importing the same table without borders is achieved in less than a second which may be seen with the attached "table without borders.html".

When the <sectPr> element is not defined as the last child element but appears in different position of the <body> of the document, the content after <sectPr> is not imported. 

Although some applications handle this case, according to the Office Open XML specification, the sectPr element must be the last element inside the <body>.

Add support for character spacing. Currently, such spacing cannot be set and are not imported.

The API should allow the client to navigate to an empty block container and manipulate it.

The block containers are Section, TableCell, Header, Footer, Comment.

The API should also include manipulation methods for a table like:

Add a row to a table.
Add a cell to a row.
Add a table to an empty cell.
Add a paragraph to an empty cell.
Add a run to an empty cell.
add a text to an empty cell.
Move to a next/previous cell.
Move to a next/previous row.

The API should use the currently applied editor formatting when creating the specified document elements.