←back to thread

235 points volemo | 5 comments | | HN request time: 0.412s | source
1. pjmlp ◴[] No.43517178[source]
It is only kind of true, PDF does everything that HTML does, with print quality, naturally one needs Adobe proper for the full feature set, as most readers only implement the standard partially, for various reasons.
replies(2): >>43518120 #>>43520662 #
2. xworld21 ◴[] No.43518120[source]
The accessibility and reflowability of HTML content, not to mention the ability to customize color schemes, fonts, line spacing, and similar are not possible with PDF, even using Adobe software. Even using the latest PDF 2.0 standard, you are ultimately expected to convert it to HTML if you need all that flexibility (such as via https://ngpdf.com/).
replies(1): >>43518892 #
3. pjmlp ◴[] No.43518892[source]
I feel we are splitting airs here, and there is the whole FOSS versus Adobe thingie,

https://helpx.adobe.com/acrobat/using/reading-pdfs-reflow-ac...

replies(1): >>43522841 #
4. Finnucane ◴[] No.43520662[source]
Getting PDF up to WCAG standards is a painful and arduous task.
5. xworld21 ◴[] No.43522841{3}[source]
I posted this in another thread

> Even the official Adobe's example of reflowing you posted before is quite bad:

> https://helpx.adobe.com/uk/acrobat/using/reading-pdfs-reflow...

> The reflowed PDF is just stacking all text and removing all non-text visual cues. For example, pairs of name/role are separated by whitespace in the PDF, but after reflowing they are undisguishable from each other (who would be the senior VP, Sunny or Daniel?). In HTML, reflowing would preserve semantically relevant whitespace out of the box.