Unplanned
Last Updated: 18 Aug 2017 10:16 by ADMIN
At this point only styling through CSS is supported. The below code does not align the paragraph to the center

            string import = "<html><body><p align=\"center\">centered??</p></body></html>";
            RadFlowDocument document = provider.Import(import);
Completed
Last Updated: 31 May 2016 13:40 by ADMIN
Workaround:

private static void WorkaroundFieldsIssue(RadFlowDocument flowdocument)
{
    foreach (FieldCharacter fieldCharacter in flowdocument.EnumerateChildrenOfType<FieldCharacter>().ToList())
    {
        // only for start
        if (fieldCharacter.FieldCharacterType == FieldCharacterType.Start)
        {
            if (fieldCharacter.FieldInfo.Separator != null && fieldCharacter.FieldInfo.Separator.Parent == null)
            {
                Paragraph parent = fieldCharacter.FieldInfo.End.Paragraph;
                int index = parent.Inlines.IndexOf(fieldCharacter.FieldInfo.End);

                fieldCharacter.FieldInfo.End.Paragraph.Inlines.Insert(index, fieldCharacter.FieldInfo.Separator);
            }
        }
    }
}
Unplanned
Last Updated: 16 Aug 2017 13:59 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: WordsProcessing
Type: Feature Request
3
Implement evaluation of = (Formula) fields (https://support.office.com/en-us/article/Field-codes-Formula-field-32d5c9de-3516-4ec3-80ed-d1fc2b5bc21d?ui=en-US&rs=en-US&ad=US ). This will allow export to PDF and HTML.
Unplanned
Last Updated: 27 Jan 2017 07:25 by ADMIN
Style properties defined in an element style selector are evaluated with higher priority over properties in a CSS class when importing from HTML.

For example if we have the following CSS style:

.sectionheading {
border: 10px solid red;
        }
td {
border: 10px solid black;
        }
and the class (.sectionheading) is applied on a table cell:

<td class="sectionheading">...</td>

The result in WordsProcessing after import of such HTML will be that the table cell has 10px black border. In MS Word and in the browsers (Chrome, Firefox...) the result will be that the cell has 10px red border.
Unplanned
Last Updated: 22 Dec 2016 13:03 by ADMIN
If the Table's TableCellSpacing property is not divided by 2 when the document is exported to Docx or Rtf, this leads to incorrect rendering after the exported document is opened with another editor (RadRichTextBox, MS Word).

Workaround: Divide by two the Table's table cell spacing property value before export to Docx, RTF formats:
foreach (Table table in document.EnumerateChildrenOfType<Table>())
{
    table.TableCellSpacing /= 2;   
}
Unplanned
Last Updated: 22 Dec 2016 13:10 by ADMIN
Table's 'cellspacing' and 'cellpadding' are not imported from HTML when the unit is not specified, e.g. <table cellpadding="25">. According to the HTML Specification (https://www.w3.org/TR/REC-html40/struct/tables.html#adef-cellspacing), the only permitted values are:
- only number
- number followed by percent.

MS Word imports it according to the specification (like WordsProcessing), but all of the browsers successfully imports values even with the px suffix, e.g. '25px'.
Unplanned
Last Updated: 03 May 2021 09:30 by ADMIN
ADMIN
Created by: Tanya
Comments: 2
Category: WordsProcessing
Type: Feature Request
3
The alternative text allows setting a description of the information contained inside the table and is useful for people who may not be able to see the content.
Completed
Last Updated: 08 Jul 2019 10:43 by ADMIN
Release LIB 2019.2.708 (07/08/2019)
An ArgumentException is thrown when importing HTML containing standard and non-standard pseudo classes or pseudo elements. The concreete scenario is the following: 
.myclass::-webkit-scrollbar or .myclass::-ms-expand

The message of the exception is similar to this: "Unexpected character found at position [X]: ".. scrollbar::>>-<<webkit-scrollbar"". 
Unplanned
Last Updated: 17 Oct 2017 08:09 by ADMIN
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>.
Unplanned
Last Updated: 22 Jan 2018 09:53 by ADMIN
When a document has a deleted text as part of track changes and there is a comment on the deletion, the document throws InvalidOperationException upon import.
Unplanned
Last Updated: 02 Apr 2018 16:01 by ADMIN
If the background color is applied to <tr> element then it is not imported.

Workaround: The background color may be applied to the cells (<td> elements) in the desired row and this should have the same effect.
Unplanned
Last Updated: 05 Jun 2018 08:27 by ADMIN
ADMIN
Created by: Anna
Comments: 2
Category: WordsProcessing
Type: Feature Request
3
There are multiple tags and attributes in the Open XML model which define the formatting of the complex script characters and are not implemented in the WordsProcessing model. 

Such tags are:
szCs: Complex script font size;
bCs: Complex script bold;
iCs: Complex script italic;

Attributes:
cstheme: Complex Script Theme Font;

The cs (Complex Script Font) attribute is implemented in the export, but it is not preserved in the model on import.
Unplanned
Last Updated: 17 Jul 2018 13:57 by ADMIN
Currently, the align attribute is supported only for a table and when applied to a cell or row is omitted on import.
Unplanned
Last Updated: 11 Mar 2019 17:39 by ADMIN

In a DOCX document, the users can define an image which is bigger than the size of the page. When such an image is at the beginning of the document and is converted with PdfFormatProvider, an additional page is added in the result PDF.

Workaround: Check the image and resize it if needed:
foreach (var image in document.EnumerateChildrenOfType<ImageInline>())
{
    var section = image.Paragraph.Parent as Section;
    if (image.Image.Height > section.PageSize.Height - section.PageMargins.Top - section.PageMargins.Bottom)
    {
        var height = section.PageSize.Height - section.PageMargins.Top - section.PageMargins.Bottom - (image.Paragraph.Spacing.SpacingAfter * (image.Paragraph.Spacing.LineSpacing - 0.97));
        image.Image.Size = new System.Windows.Size(image.Image.Width, height);
    }
}


Unplanned
Last Updated: 14 Oct 2019 12:35 by ADMIN

When applying a table or table cell border with no thickness specified, the border is exported with a default thickness value of zero. However, by specification, the default value should be 2.

Workaround: Create a border by specifying the thickness value. For example:

table.Borders = new TableBorders(new Border(thickness, BorderStyle.Single, new ThemableColor(Colors.Black)));

Unplanned
Last Updated: 03 Dec 2020 15:18 by ADMIN
When exporting a List level, which defines a Tab character between the numbering symbol and the paragraph text, Tab width should be calculated considering a Tab Stop implicitly created from the hanging indent of the List level. However, such a Tab Stop is not implicitly created, which leads to incorrectly calculated Tab distance when exporting to PDF.
Unplanned
Last Updated: 28 Jun 2021 05:11 by ADMIN
Converting table with custom borders to PDF does not work
Completed
Last Updated: 02 Aug 2021 14:24 by Marc
Release R3 2021
The <col> tag specifies column properties for each column within a <colgroup> element. It is useful for applying styles to entire columns, instead of repeating the styles for each cell, for each row. This functionality is currently not respected while importing with HtmlFormatProvider.
Unplanned
Last Updated: 11 Nov 2021 10:48 by ADMIN
The value of a content control can be resolved from an XML element stored within a Custom XML Data part in the document. Currently, WordsProcessing is unable to import all the data related to the data binding, thus cannot resolve the value of the content control.
Unplanned
Last Updated: 01 Jun 2022 07:27 by chrbra
The LockAspectRatio property of the ImageInline does not work after export to Docx