We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Word to PDF Substitution

We recently upgraded from Aspose.Words v7 to Aspose.Words v10.1. In performing this upgrade, the conversion of a document to pdf changed. No longer is the document converted to AsposePdf and then saved off as a pdf. The document now can be saved directly to pdf.


We have a client that has several templates created for mail merging. In the testing of these templates, we are noticing a lot of major differences between the rendered pdf in v7 and the rendered pdf in v10.1. As an example, we noticed that a header designed by our client uses the font ‘Monotype Corsiva’. The documents are being rendered to pdf on a server in both cases that does not contain the font in the Windows font directory. However, the old way appears to output a document with the text italicized, but the new way outputs the document with plain text. All over the document, you can notice that the font, the font size, and/or the font pitch is being changed also. The new rendered document doesn’t match up with the old one. In fact, there are several cases that are forcing the documents to be more than one page.

Since the implementation between the two versions is different due to the removal of the SaveFormat.AsposePdf, what other implementation details are suggested to control the pdf output from a Word document that was used for mail merging?

Thanks,
David

Hi
Terry,


Thanks for your inquiry. First of all, with the latest version of Aspose.Words, you can directly save MS WORD documents to PDF format. Secondly, starting from the release of Aspose.Words for .NET 9.2, the public API has undergone some changes. I think, it may be that you’re facing differences in Fonts because of these changes. I would suggest you please read the following article on How-to: Migrate to Aspose.Words 9.2 or Higher:
http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/howto-migrate-to-aspose-words-9-2-or-higher.html

Also, please note that Aspose.Words requires TrueType
fonts
when rendering
documents to fixed-page formats (PDF, XPS or SWF). For more details on How Aspose.Words Uses True Type Fonts, please read the following article:
http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/how-aspose-words-uses-true-type-fonts.html

Moreover, the latest version of Aspose.Words provides PdfSaveOptions class to specify additional options when saving a document into the Pdf format. Please visit the following link for more details:
http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/aspose.words.saving.pdfsaveoptions.html

Could you please also attach the input WORD document, you are getting problems with, here for testing? I will investigate the issue on my side and provide you more information.

Best Regards,

I have read through the links you provided, and it appears as if the code is correct in saving the document as a PDF. We are going to do some further investigation on the specific fonts that are being used to help ensure that the original output matches the current output.


One more question that I have, however, is in regards to your second note. You state (as does your documentation) that TrueType fonts are required when rendering documents to fixed-page formats. Does this mean that OpenType fonts (such as Tahoma) are not supported and/or not recommended?

Thanks,
Terry

Hi Terry,


Thanks for your request. Aspose.Words does support OpenType fonts (OTF); you can use any fonts in your documents. For more information, please visit the following link:
https://blog.aspose.com/2010/08/15/opentype-fonts-with-postscript-outlines-in-aspose-words

Please let us know if you need more information, we are always glad to help you.

Best Regards,