by georgecalm on 9/23/20, 4:18 PM with 114 comments
by EE84M3i on 9/23/20, 4:40 PM
So, IMO this is neat if it's new tech for reading PDFs and extracting data from them (and maybe leveraging current under-used features to store more machine-readable information), but bad if it's about introducing even more complexity into the PDF documents.
Perhaps 10 years from now we will have responsive PDFs, but I feel sorry for whatever damned soul is going to have to expand hard-coded limits in order to fit the new PDF specification text into a single PDF document.
by toddmorey on 9/23/20, 4:43 PM
by markonen on 9/23/20, 4:59 PM
by yegle on 9/23/20, 5:58 PM
It looks like the Liquid mode won't show up in the app if the device doesn't have Internet connection (kudos for graceful degradation here). Once you connect to the Internet and restart the app, you'll prompt to login to Adobe Document Cloud account to use this feature.
I tested a couple of PDFs and a lot of these files are showing "Liquid Mode isn't yet available for this file.", including: a Loan Estimation doc from LoanDepot, a PGE statement file, a Payment Notification from Nationwide.
It does work very well on https://www.politico.com/f/?id=00000174-abca-d59c-a174-ffde1.... Outline, concatenation of multi page sections, inline footnote reference are all working as expected.
If this works for more types of document that would be awesome.
by _coveredInBees on 9/23/20, 5:23 PM
Liquid mode is simply a tool to make it easier to consume PDF content on mobile devices. This is definitely a good thing especially since it is opt-in (you press a button to engage liquid mode in the reader).
by mrbonner on 9/23/20, 4:44 PM
by saint-loup on 9/23/20, 6:25 PM
But as a reader of essays and textbooks on a small tablet, let me tell you it's can be useful. Yeah, it's not elegant. It a clever technical solution to a real-world problem made of decades of path dependency.
You might call it a hack.
If this had been from some kid in his basement and not from a corporate press release (admittedly pompous, overselling and worrying privacy-wise), you would have cheer.
by pier25 on 9/23/20, 6:08 PM
A couple of insights from those years:
PDF is popular because it fits the paper designer mindset and because Adobe InDesign is pretty much the standard in the publishing industry.
HTML is a much better format for the digital age. It's responsive, interactive, etc, but even today, the best way to produce HTML is by using a code editor.
Even if there was a good WYSIWYG tool, editorial designers come from the paper world and have a really hard time understanding the responsive model.
Many times I've fantasized about working on a tool made for designers to produce HTML, but it would be a ton of work and I don't really think there is a market for it. Many ebook formats are actually HTML, but I think the industry is getting by with conversion tools from Word. Most HTML content comes from blogs and journals which already have an established pipeline and don't need a general purpose HTML production solution. Education is the strongest use case, but most education companies are still rooted in paper and switching to interactive education is quite a leap.
by orf on 9/23/20, 5:03 PM
by spankalee on 9/23/20, 5:19 PM
Where are the changes to the PDF format that will help other viewers understand hierarchy and relayout pages without Adobe's ML engine?
by atarian on 9/23/20, 5:29 PM
by thelazydogsback on 9/23/20, 6:25 PM
by villgax on 9/24/20, 3:33 AM
by wombatmobile on 9/23/20, 4:36 PM
by ilaksh on 9/23/20, 5:00 PM
But it really makes you question the idea of putting things into PDF format in the first place.
Because at this point it may be that a significant majority of the time PDFs are read on screens.
So in my opinion it might make more sense for acedemic journals (for example) to standardize on a something like reStructuredText (which now supports LaTeX by default). Or maybe Markdown, or a subset of HTML.
Or maybe a standard eReader (Kindle-like) format.
Or just default to a tar.gz with the RST and supporting files in standard folders.
Then if they want to publish a print journal they can automatically format it for printing. If it doesn't look good enough sometimes then let the print journals use AI or manually typeset it (earn their money).
So anyway I wish Chrome and Firefox would get support for my new RST archive format.
Point being that PDF is getting a little obsolete.
by personjerry on 9/24/20, 5:25 AM
PDFs are good for one thing only: Printing.
I wish academia would stop using PDF to distribute online, so their documents would be easier to parse!
by bob1029 on 9/23/20, 6:02 PM
Perhaps they should consider leaving PDF the fuck alone and reiterating to developers that HTML & CSS are the appropriate technologies for producing documents which must reflow based upon viewport dimensions.
by FormFollowsFunc on 9/23/20, 4:53 PM
by millzlane on 9/23/20, 4:46 PM
by masswerk on 9/23/20, 6:34 PM
This is a bit ironic, since the USP of PDF has always been its ability to preserve individual presentations in a portable format, which made it also ideal for sharing and archiving non-traditional presentations of content.
by FandangoRanger on 9/23/20, 4:48 PM
by xtiansimon on 9/23/20, 7:08 PM
I don’t see any way to improve tables in PDF. Most of the PDFs I deal with are invoices, statements, tabular reports.
As long as we’re on the topic of PDFs...what the heck is up with PDFs always asking if you want to save, even when you only opened them (no changes; using setting ‘Use only certified plug-ins’ & ‘do not show edit warnings’). Ridiculous.
by Emendo on 9/23/20, 5:21 PM
by sambroner on 9/23/20, 4:35 PM
That being said, this feels somewhat like Adobe will turn PDFs into a form of markdown where the parser is a (variable?) machine learning algorithm.
Done perfectly, the results could be great. Done badly and the results would be very painful.
by johnklos on 9/23/20, 6:43 PM
No Internet content should EVER be loaded by Adobe software by default. Ever. Their security history has clearly shown us that.
by Naushad on 9/24/20, 6:19 AM
by m0zg on 9/23/20, 5:51 PM
by currymj on 9/23/20, 6:36 PM
by fsflover on 9/23/20, 4:44 PM
by matz1 on 9/23/20, 5:04 PM
by jl6 on 9/23/20, 6:01 PM
by keeptrying on 9/23/20, 5:29 PM
It is nice though.
by mrzool on 9/23/20, 4:45 PM
I’m very skeptical but somehow intrigued.
by riazrizvi on 9/23/20, 5:24 PM
by distalx on 9/23/20, 6:44 PM
by xwdv on 9/23/20, 4:45 PM
by fierarul on 9/23/20, 5:26 PM
I'm especially enraged at the PDF "forms" XFA or whatever that no software on this planet can open except Adobe Reader. And Adobe Reader even on macOS doesn't allow Print to PDF or something else to get a PDF in a "sane" format.
I have to use a fake printer to trick Adobe Reader about this! Incredible!
by young_unixer on 9/24/20, 5:30 AM
1. AFAIK, there is no standard way to bundle a webpage containing images into a single file.
2. We have EPUB, and my experience using it has been horrible. Either the format is bad or somehow every single reader I've used sucks, and I've tried many (Foliate and the now defunct Readium Chrome extension are the ones that suck the less, but the experience is still much worse than reading a PDF)
At this point, solving the bundling problem of HTML (and using normal web browsers) seems like a better course of action than trying to use EPUB.
3. Text that always fills the width of the screen sucks if you're using a screen bigger than 10 inches.
Being able to coerce a document into a page whose border is clearly delimited (just like PDF readers do it) without having to resize windows is, in my opinion, an absolute necessity. Something like:
body { border: solid black; max-width: 25em; }
Epub readers allow defining widths (or semi-equivalently: margins) but they always look bad because there isn't a visual boundary.