Thanks for looking into this. Is there anything in the mean time that I can be doing to help speed this fix along? Is there something specific in the Word doc that is causing this? I can note, that if I use a desktop addition of Adobe Acrobat, it creates the PDFs fine.
Aspose.Words saves the provided document to the PDF incorrectly because incomplete font subsets are embedded to the document. MS Words opens this document correctly because it loads corresponding full fonts from system in this case. Aspose.Words currently doesn’t handles this case. We will fix this problem in the next release. However if you try to use this document on the system where corresponding full fonts are not installed then even MS Word will not open this document as expected.
As far as I understand the font subsets are built and embedded to the initial document when you save it in MS Word. It means that font subsets contains only characters which are used in the initial document. Aspose.Words doesn’t update the embedded font subsets when editing the document. So when you append additional pages to the initial document the embedded font subsets become incomplete.
As a workaround you could either embed full fonts to the initial document instead of subsets when saving it in MS Word or not embed fonts to the document at all.
Ok, cool. That actually helps a lot. For others interested, to remove embedded fonts in Word 2007 - 2010:
- Open up Word doc
- Go to Office button
- Click “Word Options” at bottom right of menu
- Click to “Save” section on left
- Uncheck "Embed fonts in the file"
- Click OK, then save document.