The Indent property of Table is not respected by PdfFormatProvider.
The item is duplicated. Please, follow the item at https://feedback.telerik.com/Project/184/Feedback/Details/203066
If Paragraph has applied style, and this style has associated list, and the paragraph is removed from the list locally, then on import the paragraph is added to the list. The additional numbering could be removed from the paragraph by changing its style: foreach (var p in this.document.EnumerateChildrenOfType<Paragraph>()) { if (p.ListLevel == 0) { var style = new Telerik.Windows.Documents.Flow.Model.Styles.Style("NoListStyle", StyleType.Paragraph); style.ParagraphProperties.CopyPropertiesFrom(this.document.StyleRepository.GetStyle(p.StyleId).ParagraphProperties); style.ParagraphProperties.ListId.LocalValue = null; style.ParagraphProperties.ListLevel.LocalValue = null; p.StyleId = "NoListStyle"; } }
An empty paragraph is exported with different font size than the one coming from its style. The character properties should come from the style system. Workaround: Add at least one space in each empty paragraph.
Add Borders property for a Run element and in CharacterProperties. The same is implemented for Paragraph, but in OOXML it could be applied over a Run element as well.
Table's layout type is imported as FixedWidth when it should be imported as AutoFit. The following RTF tags are not respected: trftsWidthN trwWidthBN trftsWidthBN trwWidthAN trftsWidthAN trwWidthtrftsWidthN
Field code fragment is added to the result fragment and exported to PDF/HTML format. The problem is observed when the code fragment is divided into multiple inlines. For example we have PAGE field. If 'A' is bold we would have 3 inlines (runs) in the instruction text and the issue would be observed.
Both properties table cell padding and table cell spacing are not exported to PDF format.
When some character is not supported by the font, the fallback mechanism should try finding some other font that is capable of rendering the unsupported character. However, RadPdfProcessing fallback mechanism does not always find the correct font which sometimes result in wrong glyph visualization or in missing glyph. Workaround: Font that supports these special characters may be used. This way the fallback mechanism will not be needed to export the PDF text.
The text of the watermark is exported with the default font family due to incorrect escaping while writing the OpenXML.
Implement API allowing to add watermarks without specifying its width and the height. The size could be automatically calculated using the text, its font size and font family.
Import styling properties from HTML for elements without DocumentElementProperties. For example, for ImageInline: the image has width and height and currently they could not be applied through CSS styling as the styling mechanism works only for document elements with DocumentElementPropertiesBase (RadFlowDocument, Section, Table, Paragraph, etc.)
Introduce an option to implement custom field in RadFlowDocument model (one which is not supported by the document model). In the current implementation the abstract Field class has internal abstract method which is responsible for the GetFieldResult() method and this leads to an issue when a customer wants to implement a field which we currently do not support (CustomCodeField which returns null as a result fragment).
Exporting to PDF of a table with a first cell having preferred width of 100% and a second cell having preferred width of auto will result in missing the second cell.
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.
In specific situations, a paragraph in a table cell which is last on a document page is not exported to the PDF document.
Possible workaround is adding a new paragraph to the last table cell before exporting the document.
For instance:
BlockCollection footerContent = this.document.Sections.First().Footers.Default.Blocks;
Table footerTable = footerContent.First() as Table;
footerTable.Rows.Last().Cells.First().Blocks.AddParagraph();
Content is moved from the second page to the first after applying styling to the footer and exporting to PDF format
When importing an image whose Uri is not a full Uri, an exception is thrown.
CSS style property with a numeric value will not be imported from HTML when the unit type is not specified. Example: .td{padding-bottom: 200;} This is invalid according to the HTML spec (value is optional only after 0), though web browsers and MS Word open such HTML's correctly.