I have an XML file that was created as part of another process in AsposePdf format, that I am having problems with.
The XML file has five segments, two of which only consist of one space, between the other three with parts of a name in it. (This was created from a merged document, hence the reason for 3 segments).
<?xml version="1.0" encoding="UTF-8"?>
JACK
L
SMITH
I wrote a little test harness to make sure it wasn’t any of my code:
string xmlFileName = @“C:\Temp\AsposeTest\pdf_spacing_test.aspose.xml”;
string pdfFileName = @“C:\Temp\AsposeTest\pdf_spacing_test.pdf”;
if (File.Exists(pdfFileName)) { File.Delete(pdfFileName); }
MemoryStream msOut = new MemoryStream();
Aspose.Pdf.Pdf myPdf = new Aspose.Pdf.Pdf();
myPdf.BindXML(xmlFileName, null);
myPdf.Save(msOut);
File.WriteAllBytes(pdfFileName, msOut.ToArray());
When the PDF output is produced there are no spaces between the name parts. I have attached a zip with my code chunk, xml and the PDF results for you to review. We recently just updated to the newest Aspose PDF DLL and we were not having this problem before doing so.
W
e have customers with a large quantity of documents in our system that
create this
scenario and need a resolve ASAP.
Hi,
I have tested the scenario and I am able to reproduce the same problem. For the sake of correction, I have logged it in our issue tracking system as PDFNET-16574. We will investigate this issue in detail and will keep you updated on the status of a correction.
We apologize for your inconvenience.
Is there a link that I can use to access the ticket you opened or should I just keep an eye on this forum topic?
Thanks,
-Doug
Hello Doug,
One the issue is resolved, we will notify you within this forum thread. And, as you have subscribed your email ID with this forum, an automatic email will be generated and will be sent to you. Please be patient and spare us little time.
In case I can be of any further assistance or you have any further query, please feel free to contact.
We apologize for your inconvenience.
The issues you have found earlier (filed as 16574) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.