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
39

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.
Approved
Last Updated: 12 Dec 2018 15:10 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. 

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.
In Development
Last Updated: 11 Dec 2018 07:50 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: 05 Dec 2018 11:20 by Miguel
Created by: Tanya
Comments: 8
Category: PdfProcessing
Type: Feature Request
1

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.

Approved
Last Updated: 03 Dec 2018 12:35 by ADMIN
Telerik.Windows.Zip.InvalidDataException: 'Unknown compression method (0x92)' when initializing a Telerik.Windows.Zip.CompressedStream is thrown for some object streams (read from pdf) due to incorrect transformation header.
Approved
Last Updated: 03 Dec 2018 06:18 by ADMIN
ADMIN
Created by: Deyan
Comments: 7
Category: PdfProcessing
Type: Feature Request
19
Support conversion of XPS documents to PDF using RadPdfProcessing.
Approved
Last Updated: 30 Nov 2018 14:24 by Jan
This is reproducible with specific PDF files which use custom Encoding for the fonts of the field widgets. 

WORKAROUND: Change the font of VariableContentWidgets before editing the field value. You should additionally call RecalculateContent() method of these widgets if the value of their corresponding fields is not edited. The following method may be used for changing the font of all existing widgets in the document:

private static void FixEncodingIssues(RadFixedDocument document)
{
    foreach(Annotation annotation in document.Annotations)
    {
        VariableContentWidget widget = annotation as VariableContentWidget;

        if(widget != null)
        {
            widget.TextProperties.Font = FontsRepository.Helvetica;
        }
    }
}
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: 27 Nov 2018 13:46 by ADMIN
ADMIN
Created by: Nikolay Demirev
Comments: 3
Category: SpreadStreamProcessing
Type: Feature Request
2
Provide a way to export filters.
Completed
Last Updated: 27 Nov 2018 11:29 by ADMIN
At this point, CsvWorkbookExporter flushes the data to the underlying stream each time a new data is added. This leads to decreased performance. Ensure the best possible performance by flushing the stream at the end of the content generation.

Approved
Last Updated: 23 Nov 2018 12:51 by ADMIN
ADMIN
Created by: Tanya
Comments: 2
Category: PdfProcessing
Type: Bug Report
2
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: https://feedback.telerik.com/Project/184/Feedback/Details/249535-pdfprocessing-provide-a-way-to-rename-formfields to rename the duplicate fields.
Approved
Last Updated: 23 Nov 2018 12:48 by ADMIN
ADMIN
Created by: Polya
Comments: 2
Category: PdfProcessing
Type: Feature Request
2
Provide a way to change the Name of a FormField from the RadDocument.AcroForm.FormFields collection.

As a workaround, you could create a new instance of a FormField with the desired name, add the new field in the document and remove the old one. You can use the following approach:
   1) Create a new instance of FormField (with the desired name, passed in the constructor), which will play the role of a copy of a specific FormField
   2) Copy all properties from the original field (they all vary, depending on the concrete type of the FormField, for example CheckBoxField, etc.)
   3) Create a new widget for the new field, and copy all properties from the original field's widget into the new one.
   4) Remove the original field from the RadDocument.AcroForm.FormFields collection and add the new field.
   5) Remove the original widget from the corresponding page's annotation and add the new one.

Attached is a project demonstrating this approach for a CheckBoxField.
Approved
Last Updated: 20 Nov 2018 13:55 by ADMIN
Although it is mandatory according to the specification, It seems like other applications don't require this record. Trying to open such an archive with RadZipLibrary currently throws InvalidDataException. 7zip creates such files.
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: 19 Nov 2018 18:44 by ADMIN
ADMIN
Created by: Deyan
Comments: 4
Category: PdfProcessing
Type: Feature Request
14
They are exported with the /EmbeddedFiles switch. This would allow adding external files to the PDF document.
1 2 3 4 5 6