About the contributor
PDF Association

Mission Statement: To promote Open Standards-based electronic document implementations using PDF technology through education, expertise and shared experience for stakeholders worldwide.
More contributions
Five reasons developers should participate in PDF Days Europe

PDF Days Europe, the annual PDF technology education event, will take place from 14 to 16 May 2018 in Berlin at the Hotel Steglitz International. Of the many good reasons for developers to participate, here are five of the best.

5 reasons why those implementing electronic document technologies should attend PDF Days Europe

PDF Days Europe, the annual PDF technology education event, will take place from 14 to 16 May 2018 in Berlin at the Hotel Steglitz International. Of the many good reasons for users to participate, here are five of the best.

2018 PDF 2.0 Interop Workshop

Following the success of our previous interop workshops in Cambridge, England and Boston, Massachusetts, the 3rd PDF 2.0 Interop Workshop takes place on May 16, 2018 as part of the post-conference program immediately following this year’s PDF Days Euro …

Post-Conference of PDF Days Europe 2018 in Berlin

On Wednesday, May 16, 2018, directly following PDF Days Europe, the PDF Days Post-Conference offers a variety of workshops on PDF 2.0 Interop or PDF/UA.

PDF Days Europe 2018 – schedule of sessions

Fittingly for the tenth anniversary of PDF’ becoming an ISO standard, standardization will play a significant role this year. The focus will be on recent developments, with an eye on the future. The agenda also includes PDF market analyses, next-generation PDF for mobile devices, universally accessible PDF files and the industry-supported veraPDF validator initiative.

What does “support PDF” really mean?

Microsoft Edge logo.Browsers are taking over document viewing. Where 10 or even 5 years ago users viewed PDF documents almost entirely via dedicated PDF software (often a plugin to a web-browser), today PDF files are most often viewed using implementations native to Chrome, Safari, etc., or on mobile devices.

That’s a problem, because PDF support in browsers and mobile devices is largely limited to rendering, and sometimes, incomplete rendering.

The Edge case

Microsoft released their new Edge browser in Windows 10 as the company’s replacement for Internet Explorer, the browser which took Microsoft from the very beginnings of the Internet until 2015.

The first thing to say in considering Microsoft’s Edge with respect to PDF support is that Microsoft’s development team are very open about the product’s shortcomings. This is commendable.

The Edge team posts “Standards support statements”. Pertaining to PDF, they identify (generally) the PDF features they do not fully support, or as they put it: “The Microsoft Edge product implements the PDF specifications, with variances as noted in this document.”

What isn’t supported?

As attested by Microsoft, Edge doesn’t support many of PDF’s advanced capabilities. This isn’t surprising; at this point, almost no browsers do, and it would be wrong to call out Edge for its lack of support for bookmarks, Optional Content Groups, tags, and many other features while its competition also fails to support these features.

However, the Edge team does not even claim support for the proper display of many commonplace PDF features. As of early June, 2016…

What will users experience?

The above list virtually guarantees that those viewing PDF documents with Edge will find that some pages appear other than the author intended. Some pages might be blank. Others, possibly missing images or other content.

What does this mean?

PDF is first and foremost about the reliable conveyance of a fixed-layout document. In this context the failure to support core features of the PDF specification that affect viewing is… unfortunate.

People use PDF precisely because they trust the format to display precisely the same way on any software that “supports PDF”. If users start to see blank pages or missing images they will begin to mistrust their own documents, and those they receive from others or posted on websites.

Minimum support for PDF viewing means full support for PDF rendering

Unlike HTML/CSS/JavaScript confections, the appearance of PDF is completely specified in the file itself; nothing’s left up to the implementer. You are either rendering PDF pages, or you aren’t.

Viewing software that claims to support PDF at all must, at a minimum, deliver more-or-less the same visual and printed experience as users would receive from software that supports the specification in all necessary detail.

Color-calibration and dynamic XFA isn’t the issue; there are many advanced features not all devices will support at all times. But missing or disappearing objects in conventional PDF documents? That’s not OK.

It’s bad enough that mainstream software such as Apple’s Preview ignores and destroys PDF features such as digital signatures and tags. At least Preview does a creditable job of simply rendering the page.

But what does “PDF support” mean if it doesn’t include the ability to display commonplace graphics objects appearing in millions or billions of PDF files?

What is a “portable document” anyway?

Tags: Edge, browser, rendering, viewer
Categories: Web technology