Approved
Last Updated: 11 Jan 2019 13:58 by ADMIN
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 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);
    }
}

Approved
Last Updated: 07 Jan 2019 14:49 by ADMIN
The indentation of the paragraph is wrong and the list is not aligned as expected when the paragraph in the list has all of its indentations set to 0 while the list style defines left indent.
Approved
Last Updated: 07 Jan 2019 10:00 by ADMIN
Created by: Bat-Erdene
Comments: 0
Category: WordsProcessing
Type: Feature Request
0
Add support for import of <pre> element from HTML.
 
Currently, the content of the <pre> element is imported, but the whitespaces are not preserved (and this is the main purpose of the <pre> element).
Approved
Last Updated: 28 Dec 2018 08:08 by ADMIN

When inserting content in an empty paragraph, the styles applied to it are the default document styles. However, if the properties are present in the last paragraph symbol, the content should inherit them.

Workaround: Copy the properties of the marker after inserting the content:

run.Properties.CopyPropertiesFrom(paragraph.Properties.ParagraphMarkerProperties);
Approved
Last Updated: 14 Dec 2018 12:49 by ADMIN
The background color is not respected when it is applied to part of the spans in a paragraph and the document is exported to PDF.

Html code in which the background color property is respected: <span style=""background-color:red;"">test with background</span>
Html code in which the background color property is NOT respected: 
test<span style=""background-color:red;"">test with background</span>
Approved
Last Updated: 04 Dec 2018 15:49 by ADMIN
Created by: Liu
Comments: 0
Category: WordsProcessing
Type: Feature Request
1
This element specifies the settings for the document grid, which enables precise layout of full-width East Asian language characters within a document by specifying the desired number of characters per line and lines per page for all East Asian text content in this section.

Approved
Last Updated: 27 Nov 2018 14:06 by ADMIN
Add support for setting and exporting document metadata, like Title, Author and similar.
Approved
Last Updated: 19 Nov 2018 20:20 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);
    }
}


Approved
Last Updated: 09 Nov 2018 14:23 by ADMIN
ADMIN
Created by: Deyan
Comments: 10
Category: WordsProcessing
Type: Feature Request
25
At this point the PdfFormatProvider does not support floating images and these elements are skipped when exporting to PDF.

The feature is trivial for floating images with "Behind Text"/"In Front of Text" settings, but otherwise floating images are affecting the text layout in complex ways.
Approved
Last Updated: 07 Nov 2018 13:42 by ADMIN
When a HTML has a wrong encoding set (content="text/html; charset=utf-16") we use the UTF-16 encoding when importing this HTML. This leads to wrong import. 
Microsoft Word detects that the set encoding is wrong and uses UTF-8 instead so that the imported result is correct. 

The HTML5 specification forbids the use of the meta element to declare UTF-16, because the values must be ASCII-compatible: https://www.w3.org/International/questions/qa-html-encoding-declarations#utf16 
Approved
Last Updated: 06 Nov 2018 12:35 by ADMIN
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;
        }
Approved
Last Updated: 29 Oct 2018 09:36 by ADMIN
ADMIN
Created by: Georgi
Comments: 0
Category: WordsProcessing
Type: Feature Request
0
When exporting hyperlink pointing to a bookmark, the resultant PDF document should contain Link annotation with destination pointing the bookmark's destination.
Completed
Last Updated: 26 Oct 2018 14:00 by ADMIN
ADMIN
Created by: Boby
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
When the value in the document variable collection and the argument of the DOCVARIABLE fields are with different casing, the field is not updated.

Available in LIB Version 2018.3.1029.
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.
Approved
Last Updated: 11 Oct 2018 15:41 by ADMIN
In the current implementation, the parent of a hyperlink must be a paragraph. Otherwise, a NullReferenceException is thrown.
Approved
Last Updated: 04 Oct 2018 16:03 by ADMIN
ADMIN
Created by: Deyan
Comments: 2
Category: WordsProcessing
Type: Feature Request
12
This feature includes: table of figure, table of tables etc.

TOC field contains PageRef fields inside it. To update it, we will need pagination (layout) support and PageRef fields implementation. Also TOC update can be influenced by TC fields presence in the document.

Implement export to PDF.
Approved
Last Updated: 04 Oct 2018 16:01 by ADMIN
ADMIN
Created by: Deyan
Comments: 2
Category: WordsProcessing
Type: Feature Request
8
Add support for shapes, and especially for shapes with textual content. 
In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>.
Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text.

Do not confuse these shapes with Text/Rich Text content controls (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 )
Approved
Last Updated: 02 Oct 2018 12:49 by ADMIN
This element serves as a frame and allows the element to be positioned as a floating element. More information about it is available in section 22.9.2.18 ST_XAlign (Horizontal Alignment Location) of Open Office XML.
Approved
Last Updated: 28 Sep 2018 11:43 by ADMIN
Currently the PageOrientation property is used to determine the actual size of the paper to use on the printer and does not reflect document's visualization. In order to affect Section's appearance the user should change the PageSize and PageMargin properties. For convenience the Rotate method is introduced in order to update the properties simultaneously. However the usage of the Section.Rotate(PageOrientation) method is confusing since the properties are not updated when Section.PageOrientation is already set to the same value as the parameter. Also, Rotate method is useful only for rotating already created sections, and to create section with specified pages size and margins the user should set all Section's PageSize, PageMargin, PageOrientation properties anyway.

More convenient API must be provided to create Section instances with correctly set properties for the desired page orientation.
Approved
Last Updated: 25 Sep 2018 08:53 by ADMIN
ADMIN
Created by: Tanya
Comments: 0
Category: WordsProcessing
Type: Feature Request
2
Add support for the All Caps and Small Caps properties of the runs. These properties are currently ommitted on import.
1 2 3 4 5 6