Approved
Last Updated: 16 Jan 2019 12:11 by ADMIN
ADMIN
Created by: Deyan
Comments: 4
Category: SpreadProcessing
Type: Feature Request
8
Allow to password-protect a workbook, so that it cannot be shown (read) without the password.
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);
    }
}

Completed
Last Updated: 11 Jan 2019 12:35 by ADMIN
When a chart is inserted in a document, generated by SpreadProcessing or WordsProcessing, the chart seems to lack any bars. The reason is that some theme information is missing, which effectively makes shapes take their default color, which is transparent. The same applies for shapes inserted in any Document Processing-generated OOXML documents - docx, xlsx.

Workaround: (applicable for Excel) Manually change the theme for the document in MS Excel:
- Choose Page Layout -> Themes -> Themes dropdown -> Office.
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).
In Development
Last Updated: 28 Dec 2018 14:58 by ADMIN
ADMIN
Created by: Deyan
Comments: 8
Category: SpreadProcessing
Type: Feature Request
17
Add APIs for creating and manipulating Chart objects.
Approved
Last Updated: 28 Dec 2018 12:13 by ADMIN
Exported protected document containing be opened even if the correct password is used. The same behavior is reproduced with document(without pages).
Approved
Last Updated: 28 Dec 2018 11:55 by ADMIN
ADMIN
Created by: Tanya
Comments: 2
Category: PdfProcessing
Type: Bug Report
3
When merging, only the widgets are copied but not their fields. This can lead to ArgumentNullException when exporting the document. Implement copying the fields and consider cases which include collision of names of the fields.

Workaround:
Repair the generated document using the following code:
foreach (Widget widget in this.pdfDocument.Annotations.Where(annot => annot.Type == AnnotationType.Widget))
{
    if (!this.pdfDocument.AcroForm.FormFields.Contains(widget.Field.Name))
    {
        this.pdfDocument.AcroForm.FormFields.Add(widget.Field);
    }
}
In case of Name collision, you can use the project attached to the following feedback item to rename the duplicate fields: Provide a way to rename FormFields.
Approved
Last Updated: 28 Dec 2018 10:00 by ADMIN
Created by: Lazar
Comments: 0
Category: PdfProcessing
Type: Feature Request
1
Implement functionality to support scenario when a document which already has a signature to be signed again or add two or more signatures.
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: 21 Dec 2018 07:01 by ADMIN
The appearance dictionary specifies how the annotation is presented visually on the page. If the appearance missing or is empty in PDF document NullReferenceException is thrown on import. 

Completed
Last Updated: 17 Dec 2018 13:42 by ADMIN
Created by: Stefan
Comments: 1
Category: Telerik Document Processing
Type: Bug Report
0
When two documents are merged and the source document has watermarks, these are not cloned in the target document.

Completed
Last Updated: 17 Dec 2018 12:59 by ADMIN
When documents are exported to PDF, the creation date and modification date are not expected, or, when the time zone is with negative offset, the documents are invalid (detected by validation tools).
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>
Completed
Last Updated: 13 Dec 2018 15:23 by ADMIN
ArgumentException with clarification similar to  "'\u001f', hexadecimal value 0x1F, is an invalid character." is thrown when trying to export document containing characters which are not supported in XML document - such as some control characters like 0x00, 0x1F, 0x1B, etc. Such characters are described in the XML specification here: https://www.w3.org/TR/xml/#charsets.
Although the escaped strings are not supported (see related 181318), the library could prevent the exception and export the document successfully by skipping such characters.
Workaround: remove such characters before the export. Check the following StackOverflow answer for some ideas on code for replacing the characters: http://stackoverflow.com/a/14323524/259206


Approved
Last Updated: 13 Dec 2018 04:07 by MNeverOff
ADMIN
Created by: Tanya
Comments: 40
Category: Telerik Document Processing
Type: Feature Request
41

Currently, Telerik Document Processing is available only for .NET Framework and (partially) for Silverlight. Create version targeting .NET Core.

Update: There is a version of Telerik Document Processing compatible with .NET Core 3.0 in the UI for WPF suite. You can use this version in .NET Core projects running on Windows. The assemblies can be downloaded from telerik.com, the Downloads section of UI for WPF -> Betas tab. Please, note that you should have a valid license for UI for WPF in order to be able to see this version. In case you don't, you can use the Trial license by downloading a trial version of the suite. More information about this version of UI for WPF and how it can be used is available in the related blog post.
Declined
Last Updated: 12 Dec 2018 09:21 by ADMIN

ArgumentException with clarification similar to "'\u001f', hexadecimal value 0x1F, is an invalid character." is thrown when trying to export document containing characters which are not supported in XML document - such as some control characters like 0x00, 0x1F, 0x1B, etc.

Such characters are described in the XML specification here: https://www.w3.org/TR/xml/#charsets.


Code to reproduce 
using (var stream = File.OpenWrite("sample.xlsx"))
using (var workbook = SpreadExporter.CreateWorkbookExporter(SpreadDocumentFormat.Xlsx, stream))
using (var worksheet = workbook.CreateWorksheetExporter("My sheet"))
using (var row = worksheet.CreateRowExporter())
using (var cell = row.CreateCellExporter())
{
      cell.SetValue(string.Format("Error Value: {0} ", Encoding.ASCII.GetString(new byte[] { 8 })));
}

Completed
Last Updated: 11 Dec 2018 15:22 by ADMIN
ArgumentException with clarification similar to  "'\u001f', hexadecimal value 0x1F, is an invalid character." is thrown when trying to export document containing characters which are not supported in XML document - such as some control characters like 0x00, 0x1F, 0x1B, etc. Such characters are described in the XML specification here: https://www.w3.org/TR/xml/#charsets.

Although the escaped strings are not supported (see  https://feedback.telerik.com/Project/184/Feedback/Details/190228 ), the library could prevent the exception and export the document successfully by skipping such characters.

Workaround: remove such characters before the export. Check the following StackOverflow answer for some ideas on code for replacing the characters: http://stackoverflow.com/a/14323524/259206

Fix available in R3 2018 SP1 release.
Approved
Last Updated: 05 Dec 2018 11:20 by Miguel
Created by: Tanya
Comments: 8
Category: PdfProcessing
Type: Feature Request
2

Currently, signature flags, represented by the 'SigFlags' optional entry, are not imported and exported, and there is no API for setting them.
As a result, documents signed with RadPdfProcessing (or with RadPdfViewer) appear in Adobe Reader without the blue 
document message bar at the top (the analogue of the RadPdfViewer's SignaturePanel).

If the API is supported, setting the flag to 1 or 3 would ensure that the message bar would be visualized in Adobe Reader.

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.

1 2 3 4 5 6