In Development
Last Updated: 20 Sep 2019 17:36 by Andrew
ADMIN
Created by: Tanya
Comments: 70
Category: Telerik Document Processing
Type: Feature Request
60

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: 20 Sep 2019 14:43 by ADMIN
According to the specification, the startfref keyword must be followed by the offset the xref table start on, defined on a new line. Some documents, however, have both entries defined on the same line, which leads to InvalidOperationException with message "Stack empty" while importing. Make sure this case is handled in PdfProcessing as well.
Approved
Last Updated: 20 Sep 2019 10:16 by ADMIN
Created by: Marc
Comments: 2
Category: PdfProcessing
Type: Feature Request
3
Add support for Lab color space to allow clients to import and export documents with Lab color space.
In Development
Last Updated: 19 Sep 2019 15:32 by ADMIN
The exception is caused by the charts import which is not implemented for WordsProcessing but the processing tries to import the charts part and process it.
Approved
Last Updated: 19 Sep 2019 09:15 by Roger
ADMIN
Created by: Deyan
Comments: 3
Category: SpreadProcessing
Type: Feature Request
12
Add support for conditional formatting of cells - allow applying of rules used during visualization of cells to automatically apply formatting depending on their values.
Approved
Last Updated: 17 Sep 2019 13:46 by ADMIN

Exporting document with a missing image is caused by handled Exception on import for DecodeParms containing null or stream object. Currently, PdfProcessing supports only decode parameters containing simple types. The case when some dictionary value is null or stream object should be implemented.

Another case is when the whole dictionary/stream is null. In this case, an ArgumentNullException is thrown.
Completed
Last Updated: 17 Sep 2019 13:01 by ADMIN
Release R3 2019
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;
        }
    }
}
Completed
Last Updated: 17 Sep 2019 07:30 by ADMIN
Release R3 2019
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Feature Request
7
Add support for ToUnicode CMap stream.

A side effect of not supporting it is the following: exporting PDF document which, for example, contains German umlauts, to plain text, leads to wrong characters in the resulting text.

As possible workaround, the PdfFormatProvider instance of RadPdfViewer can be used to import the document. For example:

FormatProviderSettings settings = new FormatProviderSettings(ReadingMode.OnDemand);
PdfFormatProvider pdfViewerFormatProvider = new PdfFormatProvider(stream, settings);
 
RadFixedDocument document = pdfViewerFormatProvider.Import();
 
TextFormatProvider textFormatProvider = new TextFormatProvider();
String text = textFormatProvider.Export(document);
Approved
Last Updated: 11 Sep 2019 09:02 by ADMIN
Created by: Susan
Comments: 0
Category: WordsProcessing
Type: Feature Request
1
An index lists the terms and topics that are discussed in a document, along with the pages that they appear on. 
Completed
Last Updated: 11 Sep 2019 06:17 by ADMIN
Release R3 2019

The construct <link rel="stylesheet" href="main.min.css" /> doesn't raise the HtmlImportSettings.LoadFromUri event on import, as we currently require type="text\css" to be specified explicitly.

According to mdn:
The common use of this attribute is to define the type of stylesheet being referenced (such as text/css), but given that CSS is the only stylesheet language used on the web, not only is it possible to omit the type attribute, but is actually now recommended practice. 


Think of improving the message of the exception we throw if no data is loaded.

Workaround: set type explicitly:
<link rel="stylesheet" type="text/csshref="main.min.css" />

Approved
Last Updated: 10 Sep 2019 08:08 by ADMIN
Created by: Julian Turner
Comments: 1
Category: SpreadProcessing
Type: Feature Request
1
RadSpreadsheetProcessing does not support chart color customization apart from selecting the color of the outline (set by Series.Outline.Fill). You cannot set the color of the fill of column charts etc.
Approved
Last Updated: 09 Sep 2019 17:18 by ADMIN
A TrueType font file defines a cmap table mapping the character codes to glyph indices. However, when an Encoding is defined in the font dictionary of the PDF, the defined Encoding must override the built-in cmap table. 

Currently, when a text fragment is exported with such a font the char code is mapped using the built-in cmap table and not the Encoding defined for the font, which may lead to incorrect glyphs.

Workaround: Change the font  of the TextBoxField's widget appearance:
foreach (var widget in field.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
}
Approved
Last Updated: 09 Sep 2019 14:28 by ADMIN

HtmlFormatProvider does not maintain all the whitespaces on import even though {style="white-space: pre;"} was set.

Approved
Last Updated: 06 Sep 2019 10:13 by ADMIN
ADMIN
Created by: Deyan
Comments: 7
Category: WordsProcessing
Type: Feature Request
21
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: 05 Sep 2019 12:45 by ADMIN
By specification when a form field is merged with the dictionary of the widget annotation, a Kids parameter can be existent if there are more than one widget annotations for that field. Support for importing such a fields should be added. 
Approved
Last Updated: 04 Sep 2019 10:44 by ADMIN
By specification the widget annotation and its content can be merged into the field dictionary. When merged widget with Kids property is imported an InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Annotations.WidgetObject' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Forms.FormFieldNode'.' is thrown.
Declined
Last Updated: 03 Sep 2019 15:12 by ADMIN
Created by: Antony
Comments: 1
Category: PdfProcessing
Type: Feature Request
1

I would like to request an example of the RadPdfProcessing library utilizing a Line Chart similar to how the Bar Chart is drawn in this example. 

Additionally, it would be great if there was an example with multiple charts on one page.

Thank you!

Approved
Last Updated: 02 Sep 2019 08:44 by ADMIN
The HtmlFormatProvider currently doesn't support borders for p elements.
Approved
Last Updated: 30 Aug 2019 11:06 by ADMIN
Created by: Brittany
Comments: 0
Category: SpreadStreamProcessing
Type: Feature Request
0
Add support for cell border thickness.
Approved
Last Updated: 28 Aug 2019 17:46 by ADMIN
A paragraph containing multiple Hyperlinks inside Fields with missing End FieldCharacter, leads to OutOfMemoryException: 'Exception of type 'System.OutOfMemoryException' when exporting to PDF.

Workaround: Iterate all FieldCharacter instances and move any End FieldCharacter instance to paragraphs with Start FieldCharacters. See the attached project.
 
1 2 3 4 5 6