Great to hear from you. Thank you for your post.
We have made progress with this issue and things should be much better for new articles created or pasted within InstantKB 2015 and above. We improved this with InstantKB 2015 but it will only work for new articles created within InstantKB 2015.
If your testing with a migrated article from an earlier version of InstantKB you may still see this issue even within InstantKB 2015.
You can find further information to help troubleshoot articles and a complete description of why this happens here
If your using InstantKB 2015 and wish to resolve existing migrated articles from earlier version of InstantKB it's possible to have InstantKB re-parse these articles to hopefully ensure they will export correctly as a PDF.
I would suggest editing the migrated article within the InstantKB 2015 Agent CP. Cut the entire contents of your article within the "Design" view of the editor. Place your cursor within the editor and hit CTRL+A to select all. Then press CTRL+X to cut the entire consents of the article into your clipboard. This should leave you with an empty editor. Now paste your article back into the editor using CTRL+V to re-parse. Depending on the contents of your article you may receive a prompt when pasting into the editor to remove formatting from MS Word. I would suggest accepting this prompt and allowing InstantKB to clean up formatting.
Please let me know if this helps you get your existing migrated articles working.
Also depending on the trust level of your application InstantKB will use a different PDF parser to generate the exported PDF. If your able to run InstantKB under full trust you may see better results with the export to PDF option. By default InstantKB targets medium trust however you can change the trust level via the InstantKB web.config file. You will need to add a <trust level="Full"> element within the <system.web> element like so...
Again this is completely optional but you may see better results with the Export To PDF feature.
If I can assist further of course please don't hesitate to respond,
firstname.lastname@example.orgBlog | Community