We want to display and print XFA PDF documents created with Adobe Lifecycle, within a viewer.
Therefore we flatten XFA PDF files as described in the documentation (change doctype dynamic to standard)
Using document As Pdf.Document = New Pdf.Document(New System.IO.MemoryStream(source_data))
If document.Form.Type = Pdf.InteractiveFeatures.Forms.FormType.Dynamic Then document.Form.Type = Pdf.InteractiveFeatures.Forms.FormType.Standard
document.Save(destination_file)
End Using
Now the problem. When we have an existing PDF with rounded corners somewhere in the document, after flattening these rounded corners are disappeared.
See the attachements.
XFA with rounded corners (upper right corner)
Result without the rounded corners.
When i do the same flattening from dynamic to static instead of standard, the rounded corners still exist, but not all the XFA data is removed, so it is not fully flattened.
Also printing of these files with Aspose.Pdf.Facades.PdfViewer has the same problem. When printing the file the rounded corners are lost.
We use version V10.1.0.0 library Aspose.Pdf
Hi Rene,
Thanks for contacting support.
I have tested the scenario using latest release of Aspose.Pdf for .NET 10.2.0 in Visual Studio 2012 application with target platform as .NET Framework 4.0 running over Windows 7 (x64) and I am unable to notice any issue. Can you please try using the latest release.
For your reference, I have also attached the resultant file generated over my end.
[C#]
Aspose.Pdf.Document document = new Aspose.Pdf.Document(“c:/pdftest/XFA_Form.pdf”);<o:p></o:p>
document.Form.Type = Aspose.Pdf.InteractiveFeatures.Forms.FormType.Standard;
document.Save(“c:/pdftest/XFA_Form_Standaed.pdf”);
Hello,
We downloaded the latest version on friday.
We downloaded the Aspose.Total pdf.
I saw that the Aspose.Pdf was updated on friday and the Total version today.
The bug is fixed in the latest version
Thx for the support
Hi Rene,
Aspose.Pdf for .NET 10.2.0 was published late Friday evening. However we are pleased to hear that your issue is resolved with latest release.
Please continue using our API’s and in the event of any further query, please feel free to contact.