Hi Ralph,
Hi,
Here are the Word and PDF documents. You can see the question mark characters in page 14 of the PDF (3rd column has a lot). The font is Calibri which is installed on the server. The characters are LineFeeds, I think.
Thanks!
Hi Ralph,
Here attached is a screenshot showing both the Acrobat version info and some of the question mark characters CIRCLED IN RED. They were also in the PDF I uploaded earlier.
How can I find out if I am actually using the 14.4.0 version of Aspose.Words? Maybe I did not install it or change the reference correctly. I am using the new license you provided though. Shouldn’t that only work with the new version?
I never found any upgrade instructions to follow, so I just ran the MSI and re-referenced the DLLs from inside Visual Studio. How can I verify the version? Thanks.
Hi Ralph,
- Open your PDF document with Adobe Acrobat
- Click on the ‘File’ menu and choose ‘Properties’ to open ‘Document Properties’ dialogue box.
- In the ‘Decsription’ tab, under ‘Advanced’ section, you’ll see ‘Pdf Producer’ name.
Hi Again,
It looks like I am still using 14.3.0.0.
I am attaching a confusing screenshot, but in there it appears that the .msi install did not update the .dll to 14.4.0
Thoughts?
Hi Ralph,
Hello, I did the uninstall from Control Panel, reinstalled from the MSI noted above. I removed the references from .Net and then re-added them. I am still showing PDF Producer: Aspose.Words for .NET 14.3.0.0 in Acrobat. And the question mark boxes are still in the PDF.
For Words and Cells I added the reference to the .Net 2.0 version. Is that correct? I thought I remembered that for .Net 4.0 I am supposed to use the net2.0 and not 3.5 version. Is that the problem?
I just removed the bin\net2.0 reference and added it back in from bin\net3.5_Client Profile (see attached). I got tame result in the PDF. Still 14.3.0.0 with bad characters. Any other suggestions? Thanks!
Hi Ralph,
Hi, I created a new .Net project and opened a .doc and resaved it as a .PDF, and Adobe Reader still reports it as PDF Producer: Aspose.Words for .NET 14.3.0.0.
So, somehow I have the wrong .dll installed in C:\Program Files (x86)\Aspose\Aspose.Words for .NET\bin\net3.5_ClientProfile?
Can we do a shared session where you might be able to verify the Aspose.Total installation?
It seems like the wrong version of Aspose.Words is packaged with Aspose.Total.
How about if I download the Words installer only, and install that over 14.3.0.0? I can do that without uninstalling the rest of Aspose.Total, right?
Hi Ralph,
Hi, well the good news is I downloaded & reinstalled Aspose.Words ONLY, and now I do have ver. 14.4.0.0 running. The bad news is I am still getting the Question Mark characters in the Word saved-as-PDF document.
Please see the 3 attachments. There is a .jpg with those characters circled and showing the PDF Producer version. And I am attaching the Word document, and the PDF it was saved as, where the characters in question (…) appear.
Thanks for more help to come!
Hi Ralph,
Yes, I had identified them as LineFeeds in my posting on 5/6/2014. I am using Visual Studio 2010, and it is a Windows Server 2008.
I tried saving the Word doc as a PDF using Word 2007 and I also got the ‘?’ characters.
At this point I’d like to know if we can get a refund of our $1500 upgrade of Aspose.Total, because we only did the upgrade to resolve this problem. I stated that in my posting on 5/3.
Can we get a refund? Thanks.
Hi Ralph,
Document(MyDir + “District681-052414-033133LCAP.doc”);
MemoryStream docxStream = new MemoryStream();
doc.Save(docxStream, SaveFormat.Docx);
Document docx = new Document(docxStream);
docx.Save(MyDir + “out.pdf”);
Great, thanks for that solution. I had also discovered a code-around solution which is to apply the following replace command to each string being written that may contain the LineFeeds:
s = s.Replace(Chr(10), Chr(13)) : s = s.Replace(Chr(13) & Chr(13), Chr(13))
But your interim Save as Docx is easier and safer.
Hi Ralph,