Completed
Last Updated: 15 Feb 2018 16:53 by ADMIN
The issue is observed with tables that have a specific width (in inches or percents) but whose columns do not have width specified. MS Word renders such tables expanded to their full width. For tables with 100% width, they have to expand to the entire width of the page. The same behavior is expected in the PDF export.

As a common side effect, when specific text alignment (e.g. center or right) is applied to a paragraph within a table cell, and the table is with specified width, but the column is auto-sized (without set width), then the text alignment seems as not respected. Actually the problem is that the column table is shrunk to the text width.

Workaround: this may be used before exporting the RadFlowDocument instance to PDF:

foreach (Table table in document.EnumerateChildrenOfType<Table>())
{
    table.LayoutType = TableLayoutType.FixedWidth;
}


Workaround 2:

Set specific width to the auto-sized columns (to any of the cells in the columns):

cell.PreferredWidth = new Telerik.Windows.Documents.Flow.Model.Styles.TableWidthUnit(500);

Available in R1 2018 SP2 release version.
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);
            }
        }
    }
}
Completed
Last Updated: 24 Jun 2016 15:13 by ADMIN
Completed
Last Updated: 14 Jun 2016 07:29 by ADMIN
ADMIN
Created by: Deyan
Comments: 1
Category: WordsProcessing
Type: Bug Report
2
Styled text in a list item <li> is imported as a different paragraph. The result is split of the text into multiple paragraphs which are not in a list.

The issue could be observed only when the text is written as a direct content of the <li> element. If it is in a <p> element the paragraph is imported correctly (it is not split). 

For example:

problematic html (the paragraph will be split) - <li>An appointment may create any provisions <strong>and</strong> in particular: </li>
non-problematic html (the paragraph will be imported as it should) - <li><p>An appointment may create any provisions <strong>and</strong> in particular: <p></li>
Completed
Last Updated: 01 Jun 2016 15:55 by ADMIN
If we have a list (<ol>, <ul>) with list items (<li>) and there is a paragraph inside a list item(<p>), an empty additional paragraph is imported if the <p> element is right next to the <li> element (without a space). The indentation of child paragraphs in list item could be messed up as well. If there is a space between the HTML elements, the content is imported as expected.
Completed
Last Updated: 31 May 2016 16:24 by ADMIN
When importing an image whose Uri is not a full Uri, an exception is thrown.
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"". 
Completed
Last Updated: 14 Feb 2019 15:31 by ADMIN
When MergeField is present in the document, and this merge field is evaluated to an empty string - this, for example, happens when the property in the data source is set to null, empty string, or is missing at all - the result fragment remains in the result document. Instead, it should be removed.

Steps to reproduce: 
- Create document with merge field, the field should contain result fragment, and set data source which contains null or string.Empty value for the field:

            RadFlowDocument document = new RadFlowDocument();
            RadFlowDocumentEditor editor = new RadFlowDocumentEditor(document);

            editor.InsertField("MERGEFIELD FirstName ", "«FirstName»");

            List<Person> source = new List<Person>()
            {
                new Person() { FirstName = string.Empty }
            };

            RadFlowDocument mergedDocument = document.MailMerge(source);
Expected: The result document is empty.
Actual: The result document contains "«FirstName»" string.

Available in LIB Version 2017.3.1120.
Completed
Last Updated: 16 Oct 2018 14:19 by ADMIN
A NullReferenceException is thrown when importing a hyperlink that doesn't contain any run elements. Similar hyperlinks could be skipped so the document can be successfully imported. 

Available in R3 2018 SP1 release.
Completed
Last Updated: 23 Apr 2018 07:06 by ADMIN
Run's default constructor creates it with Text = null. When document with such run is exported to PDF, NullReferenceException is thrown.

Workaround: Create the Run and immediately set its Text property to string.Emtpy.

Available in LIB Version 2018.1.423.
Completed
Last Updated: 13 Mar 2019 10:59 by ADMIN
By specification, the src attribute for images in the HTML content must be present and must contain a valid non-empty URL potentially surrounded by spaces.

However when embedded images with leading white spaces are imported, UriFormatException: 'Invalid URI: The Uri string is too long.', is thrown.
Completed
Last Updated: 07 Aug 2019 13:23 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
Created by: Blane Bunderson
Comments: 0
Category: WordsProcessing
Type: Bug Report
1
Hyperlinks created via HtmlFormatProvider are not properly exported to PDF and cannot be clicked.
Completed
Last Updated: 31 Jul 2019 08:24 by ADMIN
Release LIB 2019.2.805 (08/05/2019)
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.
Completed
Last Updated: 07 Aug 2019 10:57 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
When the document contains an image that is defined as an external resource but is not available in the specified location and cannot be found, a KeyNotFoundException is thrown. Handle this exception and replace the missing image with a default one for such cases. Consider exposing an option to notify the user about this error.
Completed
Last Updated: 06 Aug 2019 13:26 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
When the imported html contains an attribute of the type width="", Wordsprocessing throws ArgumentException and does not import the document. 
Completed
Last Updated: 14 Dec 2017 15:49 by ADMIN
Although this is not a valid table scenario we should not throw an exception when measuring and exporting such table.

Fix available in LIB Version 2017.3.1218.
Completed
Last Updated: 14 Jun 2016 07:29 by ADMIN
Workaround:
Copy the default styles after the Mail Merge

RadFlowDocument merged = sourceDocument.MailMerge(mailMergeSource);
merged.DefaultStyle.ParagraphProperties.CopyPropertiesFrom(sourceDocument.DefaultStyle.ParagraphProperties);
merged.DefaultStyle.CharacterProperties.CopyPropertiesFrom(sourceDocument.DefaultStyle.CharacterProperties);
Completed
Last Updated: 02 Jun 2016 05:09 by ADMIN
ADMIN
Created by: Deyan
Comments: 1
Category: WordsProcessing
Type: Bug Report
1
If the value from the source contains new lines, they should be inserted in the resulting documents as new paragraphs.
Completed
Last Updated: 13 May 2016 19:58 by ADMIN
ADMIN
Created by: Deyan
Comments: 1
Category: WordsProcessing
Type: Bug Report
0
ParagraphMarkerProperties of a Paragraph element are not cloned and this leads to incorrect list numbering (bullets) rendering after export since the numbering styles (bullets, numbers and etc.) copy the style properties from there.
This affects Clone() method of the Paragraph and ergo RadFlowDocumentEditor.InsertDocument() method and DocumentElementImporter.Import() methods since they're using Clone() method internally.
1 2