Aspose.Pdf.Generator.Pdf API is gone

Aspose.PDF Product Family
1

Hi, we have run into an issue after upgrade from older versions of apsose.pdf to latest 17.10.
The old Aspose.Pdf.Generator.Pdf API is gone in 17.10 and also the old xml template format to build pdf docs.
Old format
https://docs.aspose.com/display/pdfnet/Use+Xml+as+Template
New format
https://docs.aspose.com/display/pdfnet/Aspose.Pdf+Articles#Aspose.PdfArticles-PDFDocumentStructure

This is the the xml format that we used in the in the Aspose.Pdf.Generator.Pdf API
AsposeXMLTemplate.zip (1.1 KB)

Do you have migration information to build up the same document with the new DOM API?
Best Regards
Per Rodstrom

2

@perRodstrom,

We are investigating your old XML template and require little time. We will get back to you soon.

3

@perRodstrom

Thanks for your patience.

We have tried to convert your XML template according to new DOM based structure, by following the XML Schema (.xsd) provided with the API and managed to produce similar output PDF document. Please check attached PDF document and XML (DOM) template. Regarding XML Schema, you can find it in XML folder, located in Aspose.Pdf installation directory. However for your convenience, we have attached XML Schema file as well.

Document doc = new Document();
doc.BindXml(dataDir + "AsposeXMLTemplate_DOM.xml");
doc.Save(dataDir + "AsposeXMLTemplate_DOM.pdf");

Aspose.Pdf.zip (1.6 KB)
AsposeXMLTemplate_DOM.zip (1.2 KB)
AsposeXMLTemplate_DOM.pdf (3.4 KB)

You can migrate your existing XML templates to DOM based XML structure, by following the element sequence in XML Schema. In case you face any issue, please feel free to let us know.

4

Hi I have started with porting from generator to DOM and I need help information on how to be able to do simulate or alternativ to generators Replaceable symbols.
We use the following:
#$NL Line break in Cell
#$UNICODE(160) Non-breaking space
What can we do to simulate this in DOM xml?
Best Regards
Per Rodstrom

5

@perRodstrom

Thanks for your inquiry.

Would you please share a sample XML template where you are using these symbols and they are not taking any effect. We will test the scenario in our environment and address it accordingly.

6

ComputasPerRodstrom.zip (149.4 KB)
Hi, I have uploaded the pdf and also the dom xml that shows the problems…

  1. #$UNICODE(160) is ignored and shows in the pdf
    2)#$NL is ignored and shows in the pdf
  2. IsKeptWithNext Table attribute is ignored and the table shows in two different pages.
    This used to work in aspose.Generator.
    Best Regards
    Per Rodstrom
7

@perRodstrom

Thanks for sharing the sample files.

We have tested the scenario in our environment and managed to observe the same issue. For sake of detailed investigation, we have logged these issues in our issue tracking system as follows:

PDFNET-45325

PDFNET-45326

We will investigate logged issues in details and keep you informed with the status of their rectification. Please be patient and spare us little time.

We are sorry for the inconvenience.

8

Hi, do you have any update on this case?
Best Regards
Per Rodstrom

9

@perRodstrom

Thanks for your inquiry.

We would like to share that issue PDFNET-45325 has been resolved in 18.10 version of Aspose.PDF for .NET which will be rolling out next month. As soon as fix-in version is available for download, we will surely notify you.

However, the issue PDFNET-45326 is still pending for resolution due to long queue of issues in the queue. As soon as some definite updates regarding its resolution is available, we will share with you. Please spare us little time.

We are sorry for the inconvenience.

10

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