If a PDF with a TextBoxField is created with a corresponding Widget, the text is actually long enough to be broken in more than one line and AllowScroll is set to true, upon opening the file in Adobe, the text is not visible. The field actually does have an appearance which can be seen upon inspection of the document but for some reason it is not visualized.

Another issue seems to be a different manifestation of the same problem: When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly. 

In business or enterprises there is more and more demand for PDF/A-3.

In Germany it is Zugferd for hybrid invoices, in Brazil Nota Fiscal Eletronica 2.0, in France FACTUR-X.

Also for longterm preservation it is import to support PDF/A-3.

If I would be the PM of this library this would be my number one priority!

Currently, there is internal API which is used by RadWordsProcessing PDF export functionality. We should consider making appropriate public API which would expose tab stops editing functionality.

This allows specifying a soft mask in the external graphics state.

Some customers need to export a single page of the PDF document to plain text. Expose such a possibility so the customers don't need to export the whole document.

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).

When importing document with predefined ToUnicode CMaps (e.g. Identity-H), an InvalidCastException is thrown with cause: 

Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.CMaps.ToUnicodeCMap'.

Allow the customers to insert DWG files in the PDF documents.

Some documents result in glyphs with wrong widths after import-export. Widths are mixed making some of them to overlap and others to have bigger distance.

Support for exporting WMF (Windows Metafile) and EMF (Enhanced Metafile) images should be implemented.

Workaround: Convert the WMF images to PNG before exporting:

Importing document containing TextBox widgets with NormalContentSource defining text properties, such as FontSize and Position, are exported with incorrect appearance when the value of the field is modified.

These permissions are defined on a document level and apply permission handlers. The permission handlers are similar to the security handlers but do not require the document to be encrypted. They are also used to determine which objects are to be included in the digest calculation used for the digital signature functionality.

We would like to search a PDF document for specific text and returns its position. We generate PDF reports using Telerik Reporting which contain placeholders that are replaced with images and text at run-time. It appears the logic has already been implemented, but the implementing classes (e.g., TextSearch, TextRecognizer) aren't accessible. Please consider making this capability available.

The values of rotated widgets on a rotated page are invisible after exporting them. The value can be seen only while editing a field.

Hello Telerik,

Last time we attempted this the <Viewbox> contents would not render and were empty upon xaml to pdf output. It would be great if you had this feature and we could move completely away from raster output to PDF for controls that contain Viewboxes. Otherwise we have really liked the PDF's created by the tool, the vector output is sharp as expected.

Thank you,

Patrick

A KeyNotFoundException is thrown when trying to open a PDF containing specific Type1 font.

Currently Type0Font class has CMap that can only be Identity-H. The Identity-V is a vertical version of Identity−H. The mapping is the same as for Identity−H.

When the document contains Simple Font with predefined encoding and no ToUnicode mapping the text should be extracted with the following algorithm:

• Map the character code to a character name according to the font’s Differences array.
• Look up the character name in the Adobe Glyph List to obtain the corresponding Unicode value. 
  

Currently, the PdfProcessing library doesn't map the character code properly which leads to wrongly encoded text content.

More information is available in the Pdf Reference 1.7. Page 442 lists all predefined CMaps that should be imported and exported as PdfName objects. At this point, trying to import a document with such encoding, a NotSupportedException is thrown with message Encoding type is not supported.

When importing a VariableContent widget with OpenType font, which fails to read the post table of the font file, a NullReferenceException is thrown when the RecalculateContent() method is called.

Workaround: Change the widget font:

foreach (Widget widget in textBoxField.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
    widget.RecalculateContent();
}