[toddmorey]

When your digital document format needs artificial intelligence to understand the content, it may be the wrong container for delivering content. I'll be sad to see content that should be delivered as HTML instead delivered as liquid PDF.

[alanbernstein]

According to this article, nothing will be "delivered" as liquid PDF, because it's a feature of the reader app, not the document.

The point is that there are 30 years worth of existing, static, PDF documents - published as PDF for a potentially valid reason - which are frustrating to read on a mobile device.

[latortuga]

I'm not convinced this is even a feature of the reader app. When they click "Liquid Mode", it says "Processing in Document Cloud" which means they're sending all your PDFs to their servers? Make sure you don't click Liquid Mode on any sensitive documents!

[tasogare]

The PR post states near its end that the more documents go through Adobe Sensei the better it will get. So yes, they’re mining third party data. It would be interesting to see if this is GDPR compliant (I bet no since user is not well informed about the processing).

[wombatmobile]

If the AI is built in to a client side reader, that reader has to be installed on all clients, then kept up to date.

A frictionless solution would be for Adobe to offer the AI as a web service that renders legacy PDF files as HTML.

[snowwrestler]

I would prefer that my device does not phone home to Adobe about every single PDF I decide to look at on my phone. On-device rendering for me, please.

[wombatmobile]

It would be opt-in only, to respect your wishes.

[copperx]

I am old to remember that the initial publicity surrounding PDF touted it as the future of the web. A better HTML.

I laugh now as I laughed back then.

[barumi]

Perhaps that was the case in the pre-HTML5 days, where each browser decided what they think they thought was HTML, and IE was a reference.