Approved
Last Updated: 31 Jan 2019 13:30 by ADMIN
ADMIN
Created by: Tanya
Comments: 4
Category: PdfProcessing
Type: Bug Report
7
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 attached project or the attached project to the following feedback item to rename the duplicate fields: Provide a way to rename FormFields.
Approved
Last Updated: 22 Jan 2019 16:20 by ADMIN
The case is invalid according to the specification but all readers manage to open the document and allow editing its fields. The document can be also opened in RadPdfViewer but without the fields and the widgets.
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. 

Approved
Last Updated: 06 Nov 2018 14:39 by Georgi
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'.
Approved
Last Updated: 27 Sep 2018 13:22 by ADMIN
This happens only in cases when the Radio flag is not set and there are multiple widgets with different "ON" state names.
Approved
Last Updated: 04 Sep 2018 12:35 by ADMIN
The issue may be reproduced by opening the attached PDF in Adobe Reader. Although the viewer initially shows the characters correctly, when you start typing in the TextBox, the umlaut/diacritics characters get corrupted. In other PDF viewers, the umlaut characters are handled correctly, so the issue seems to related to concrete Adobe Reader encoding handling implementation. The diacritic characters are handled incorrectly in other viewers as well (e.g. Chrome).
Approved
Last Updated: 24 Aug 2018 12:22 by ADMIN
We should implement the logic for getting character codes from Unicode when using CFFFontSource.

Workaround: The font may be changed by creating a similar font with FontsRepository.TryCreateFont(...) method.
Approved
Last Updated: 11 Jul 2018 14:50 by ADMIN
ArgumentException is thrown while importing a choice field whose value is an empty string. Instead, the empty string should be imported.
Approved
Last Updated: 31 May 2018 16:09 by ADMIN
The only applied graphics properties are the fill color, the stroke color and the rendering mode (which specifies whether the glyph is filled or/and stroked). Instead, Block and FixedContentEditor classes should apply all other graphics state properties (StrokeThickness, MiterLimit, StrokeDashOffset, StrokeDashArray, StrokeLineJoin, StrokeLineCap).

WORKAROUND: These properties may be applied after the text content is added. For instance, if you require changing the StrokeThickness of the text fragments which are stroked and not filled then you may use code similar to the one below:

foreach (RadFixedPage pages in document.Pages)
{
    foreach (TextFragment textContent in pages.Content.Where(c => c is TextFragment))
    {
        if (textContent.RenderingMode == RenderingMode.Stroke)
        {
            textContent.StrokeThickness = 0.3;
        }
    }
}
Approved
Last Updated: 25 Apr 2018 08:54 by ADMIN
This exception seems to be related to AES algorithm PaddingMode property. 
Approved
Last Updated: 20 Apr 2018 15:19 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Bug Report
0
The Matrix property seems to be incorrectly interpreted during the import process.
Approved
Last Updated: 06 Apr 2018 15:26 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: PdfProcessing
Type: Bug Report
0
For some documents, the clippings and colors of the geometries are modified on an import-export scenario.
Approved
Last Updated: 19 Mar 2018 14:17 by ADMIN
ADMIN
Created by: Tanya
Comments: 3
Category: PdfProcessing
Type: Bug Report
1
The letters are disordered after the file is exported using PdfFormatProvider.
Approved
Last Updated: 03 Jan 2018 13:34 by ADMIN
This exception corrupts the whole document import. Instead, we should provide Exception handling mechanism which allows the user to import the rest of the content.
Approved
Last Updated: 18 Dec 2017 11:25 by ADMIN
According to PDF specification, the field value should be specified in the "V" entry of the corresponding PDF dictionary. However, some PDF producers are skipping this entry and are setting only the Widgets appearance states. As most viewers manage to show the radio button and checkbox as selected, we should handle this scenario and import the field values based on the related widgets when this value is not explicitly set with the field's V entry.
Approved
Last Updated: 07 Nov 2017 07:39 by ADMIN
InvalidOperationException is thrown when exporting font that is available but not used.

The stack trace is as follows:
   at System.Linq.Enumerable.Max(IEnumerable`1 source)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.Cid.CidSet.CopyPropertiesFrom(IPdfExportContext context, FontBase font)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor.CalculateCidSet(IPdfExportContext context, CidFontBase font)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor.<>c__DisplayClass34.<CopyPropertiesFrom>b__30()
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Utilities.PdfObjectsExtensions.ToPrimitive[P,T](PdfProperty`1 pdfProperty, Func`2 convertToPrimitive, Func`1 getDefaultValue)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontDescriptor.CopyPropertiesFrom(IPdfExportContext context, FontBase font)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontObject.CopyPropertiesFromOverride(IPdfExportContext context, FontBase font)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.CidFontObject.CopyPropertiesFrom(IPdfExportContext context, FontBase font)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Elements.Fonts.Type0FontObject.CopyPropertiesFromOverride(IPdfExportContext context, FontBase font)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExporter.WriteFontsFromContext(PdfWriter writer, IPdfExportContext context)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Export.PdfExporter.Export(IRadFixedDocumentExportContext context, Stream output)
   at Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.PdfFormatProvider.ExportOverride(RadFixedDocument document, Stream output)
   at Telerik.Windows.Documents.Common.FormatProviders.FormatProviderBase`1.Export(T document, Stream output)
Approved
Last Updated: 12 Oct 2017 08:26 by ADMIN
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. 
Approved
Last Updated: 10 Jul 2017 13:01 by ADMIN
According to PDF specification widget's parent field should always be terminal field and should have FieldType specified. However, there are documents which are generated without fulfulling this rule and we need to consider handling this scenario without any exceptions.
Approved
Last Updated: 26 Apr 2017 10:04 by ADMIN
This is causing issues when exporting the document to PDF from WordsProcessing - the pdf library tries to create the font, but cannot find it due to a different casing. When importing HTML document, the font-family property is read with small letters. Later, when converting the string containing the value, it is changed to title case. 

This issue will be reproducible with each font containing a name with a letter with casing different than the one of the other letters (exc. first capital letter), for example: Microsoft JhengHei
Approved
Last Updated: 03 Apr 2017 08:46 by ADMIN
If the MatrixPosition has Matrix (1, 0, 0, 1, 20, 10) the Table should be positioned with top-left coordinate (20, 10). Instead, it is wrongly positioned at (40, 20).