Is this a one-way publish only, or do we support opening and editing PDFs as well?

Save as PDF is a one-way "publish" operation only. We are neither shipping a special viewer nor doing any work to make PDF files readable or editable by the Office applications.

Because this functionality is native to Office applications, we can capture richer document data further upstream than we would be able to do with a print driver. For example, we annotate our PDF output with tags for accessibility and we support internal and external hyperlinks. An additional advantage to capturing document data further upstream is that we render some visual effects, such as transparency and gradients, better because we are working with native information that has not been converted to bitmap for printer output.

Yes, Office PDF output contains tags to assist with reading order for screen readers, and alternative text on images and on rasterized (bitmapped) text (to avoid interrupted text flow when portions of a text run are rasterized due to text effects or other document constructions). We also tag documents and, in some cases, text runs with language tags to assist with accurate pronunciation, and we export Unicode text for nonstandard glyphs to enable screen readers to access the actual text content. I appreciate the feedback we have received in this area as to what tags people would like to see implemented.

For our Standard intent, we both embed and subset embeddable fonts (when permitted). For our Minimum Size intent, we do not embed "Web safe" fonts, but we do embed and subset all other embeddable fonts. We are not doing font outlining in the general case.

Yes, document structure is implemented for some applications to support bookmark navigation in PDF viewers. In Word, for example, you have the option to generate bookmarks by page, by heading, or by Word bookmarks.

The post Answers to some common questions about PDF/XPS Add-in appeared first on Blog IT.