4 ms·
>...migrating my website from HTML to PDF/A. I'm genuinely curious as to how having an online presence (like a website) implemented as PDF is advantageous? Do
by mxuribe 6y ago
>...migrating my website from HTML to PDF/A.
I'm genuinely curious as to how having an online presence (like a website) implemented as PDF is advantageous? Do PDFs offer some security or authenticity of content that html lacks? Not bashing, really just want to learn.
- baud147258 6y agoI think the idea of using PDF/A is that you only have to maintain a single file that contains all the content, without external dependencies like pictures or fonts. It also supports ways to sign the file, to protect its integrity. At least it's how I understand it. Edit: following the link on the parent's profile, there's a few explanations (in https://www.lab6.com/0 https://www.lab6.com/0): """ PDF makes a stand against the churn. I’m publishing this document in PDF because: - PDFs are self-contained and offlineable - PDFs are files. - PDFs are decentralised. - PDFs are discoverable. - PDFs are independent of browsers - PDFs and a PDF tool ecosystem exist today - PDF is an open standard - PDFs are part of the web - PDFs are page-oriented """ (abridged for readability, each of the bullet points are expanded in the document)
- jl6 6y agoThank you to the sibling content for quoting the headlines from my polemic, but yes, validated PDF/A is guaranteed to contain only static content with no tracking malfeatures and a vastly reduced attack surface compared to HTML5. It’s hilariously impractical if your goal is to build a web application, so a direct comparison to HTML5 isn’t fair, but if you just want to publish information, PDF/A is state of the art.