XML import to PDF bug

This text will be hiddenAsposePDFError.zip (1.0 MB)

When importing xml data for some reason the X mark in the T5 column does not get ticked.
Attached is the XML, PDF, Picture how Adobe Imports the data, Picture what Aspose does. I believe this to be a bug. We have tried this in AsposePDF versions: 9.7/10.9/19.2

Code used to import it as follows:

FileStream xmlstream = File.Open(@“PATH…Information Disclosure Statement By Applicant (PTO SB-08)2_data.xml”, FileMode.Open, FileAccess.Read, FileShare.Read);
FileStream pdfstream = new FileStream(@“PATH…Statement By Applicant (PTO SB-08)2.pdf”, FileMode.Open, FileAccess.ReadWrite);
Document document = new Document(pdfstream);
Aspose.Pdf.Facades.Form doc = new Aspose.Pdf.Facades.Form();
doc.BindPdf(document);
doc.ImportXml(xmlstream);
xmlstream.Close();
document.Save();

@jrocke

Thank you for contacting support.

We have worked with the data shared by you and have been able to reproduce the issue in our environment. A ticket with ID PDFNET-46071 has been logged in our issue management system for further investigation and resolution. The ticket ID has been linked with this thread so that you will receive notification as soon as the ticket is resolved.

We are sorry for the inconvenience.

Good morning. I am aware that we will get notified on completion but was wondering if there is any sort of update?

Thanks

@jrocke

Thank you for getting back to us.

We are afraid any update is not available yet. We will let you know once any update will be available.

This is still an issue for us. Any update?

@jrocke

We really regret to inform that your issue could not get resolved yet. However, we have recorded your concerns and will surely consider them during investigation of the issue. We highly appreciate your patience and comprehension in this matter.

We apologize for the inconvenience.

Is there still no update on this? Is there anything we can do to help get this done? We have been having to rely on Java for the last 3 and a half years and would love to get back to Aspose.

@jrocke

Please accept our humble apology for the delay and inconvenience you have been facing. The earlier logged ticket is quite complex in nature and many API components need to be changed in order to apply fix. Nevertheless, we have raised its priority to next level and will let you know once there is some progress towards its fix.

We apologize for the inconvenience.

The issues you have found earlier (filed as PDFNET-46071) have been fixed in Aspose.PDF for .NET 22.12.