Unplanned
Last Updated: 25 Feb 2021 16:11 by ADMIN
Add support for text-transform CSS property. The values can be: none, capitalize, uppercase, lowercase.
Unplanned
Last Updated: 25 Feb 2021 16:11 by ADMIN

Add full support of the font-weight CSS property. The defined values are: normal, bold, bolder, lighter, 100, 200, 300, 400, 500, 600, 700, 800, 900. Currently bold and normal are supported.

Unplanned
Last Updated: 22 Feb 2021 14:31 by ADMIN
Created by: Vladislav
Comments: 0
Category: WordsProcessing
Type: Feature Request
0

This element specifies that an absolute position tab character shall be placed at the current location in the run content.

Completed
Last Updated: 19 Feb 2021 16:54 by ADMIN
Release R1 2021 SP1
The height of the empty paragraphs when they are exported to PDF is shorter than it should be.
Completed
Last Updated: 18 Feb 2021 15:00 by ADMIN
Release R1 2021 SP1
 ArgumentException when trying to set the font size to zero on import.
Unplanned
Last Updated: 10 Feb 2021 14:35 by ADMIN
 Add an option to export the content controls as a form fields. 
Unplanned
Last Updated: 08 Feb 2021 16:06 by ADMIN

Absolute positioning of images, defined in the class stylesheet, is not respected.

Completed
Last Updated: 29 Jan 2021 15:31 by ADMIN
Release R1 2021 SP1

The missing feature leads to this unwanted behavior:

  • When there is content control, which generates content on interaction, and it has some custom run properties set to it, they are lost when the user modifies it.

 

As a workaround, you need to apply a custom style (with the desired run properties) and apply it to the content control.

Completed
Last Updated: 29 Jan 2021 14:49 by ADMIN
Release R1 2021 SP1
When exporting to PDF the bullets of the unsorted list are missing.
Completed
Last Updated: 29 Jan 2021 14:43 by ADMIN
Release R1 2021 SP1
Image size is not respected when importing HTML
Unplanned
Last Updated: 28 Jan 2021 12:49 by ADMIN

When exporting to a PDF filea document with a header containing a watermark, set by a shape, the rest of the header content is skipped and the header is exported with default margin values.

A possible workaround could be to set the watermark as an image.

Completed
Last Updated: 26 Jan 2021 12:11 by ADMIN
Release R1 2021 SP1
When the URI source applied to the image cannot be parsed as a Path object to obtain its extension, an ArgumentException is thrown.
Completed
Last Updated: 26 Jan 2021 10:28 by ADMIN
Release R1 2021 SP1
The exception is thrown while importing an image that has any value for height property applied through a style.
Unplanned
Last Updated: 22 Jan 2021 09:00 by ADMIN

When a watermark needs more space than the available on the page, it should be resized. At this point, part of its content can be cut off as it falls outside of the page bounds.

Workaround: Decrease the size of the watermark prior to exporting it to PDF:

foreach (var section in this.document.Sections)
{
    Header header = section.Headers.Default;
    if (header != null)
    {
        foreach (Watermark watermark in header.Watermarks)
        {
            if (watermark.TextSettings != null && watermark.TextSettings.Width > section.PageSize.Width)
            {
                watermark.TextSettings.Width = section.PageSize.Width;
            }
        }
    }
}

Completed
Last Updated: 21 Jan 2021 09:33 by ADMIN
Release R1 2021
Currently, the unsupported Structured document tags (SDTs) in the document are skipped on import.
Completed
Last Updated: 20 Jan 2021 12:32 by ADMIN
Release R1 2021
ADMIN
Created by: Deyan
Comments: 19
Category: WordsProcessing
Type: Feature Request
67
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.
Unplanned
Last Updated: 15 Jan 2021 10:29 by ADMIN

When importing a document with a style set in a parent <div> element its children`s content doesn't inherit it.

Steps to reproduce:

  1. Import the following HTML string:
    <div style="background-color: green;">
    	<h1>Test heading</h1>
    	<div>Test div</div>
    </div>
  2. Export it as PDF (or any other supported format)

Actual vs Expected:
 

Unplanned
Last Updated: 18 Dec 2020 10:42 by ADMIN
According to the Office Open XML specification, the border thickness should be preserved in a DOCX file using a positive whole number, whose contents consist of measurement in eighths of a point. However, the current logic of WordsProcessing works with double values that might result in fractional numbers while converting them. 
Unplanned
Last Updated: 15 Dec 2020 15:33 by ADMIN

Currently, the content of the span of such elements  is imported:

<!DOCTYPE html>
<html lang="en">
<head>
</head>
<body>
	<div id="progressBar" style="width: 100%; display: none;" class="themed-progressbar k-widget k-progressbar k-progressbar-horizontal" data-role="progressbar">
		<span class="k-progress-status-wrap k-progress-end"><span class="k-progress-status">100%</span></span>
		<div class="k-state-selected k-complete" style="width: 100%;">
			<span class="k-progress-status-wrap k-progress-end" style="width: 100%;"><span class="k-progress-status">100%</span></span>
		</div>
	</div>
</body>
</html

Actual: the content of the spans is not skippet (100% 100%)

Expected: to be skipped

 

Completed
Last Updated: 15 Dec 2020 12:25 by ADMIN
Release R1 2021
HTML heading elements (<h1>-<h6>) are imported with the default heading styles (Heading 1 - Heading 6) for RadFlowDocument, which is unexpected, as the browsers and MS Word import them with different styling. 

For example, <h1> is imported as Heading 1 with font the following properties:

Font: Cambria
Font color: Accent 1
Spacing before: 14 pt
Spacing after: 14 pt

While MS Word imports it as:

Font: Times New Roman
Font color: not set (black)
Character spacing: Kern at 18 pt
Spacing before: Auto
Spacing after: Auto