6 ms·
One of the hardest things I remember from my time as a web consultant was explaining to my customers why PDF is not a suitable replacement for HTML. They always
by kqr 8y ago
One of the hardest things I remember from my time as a web consultant was explaining to my customers why PDF is not a suitable replacement for HTML. They always tried to replace half of their pages with pdf documents...
- tonyedgecombe 8y agoPDF is easy to create from a Word document, try using Word to create HTML and you get a dogs dinner. If our industry was better at creating tools for ordinary users to create HTML then the problem would solve itself.
- 3pt14159 8y agoThe issue is that people want a frozen format so they can line up images precisely where they want them to be. This is antithetical to displaying things in a browser. Sure, it can be done, but it's CSS that's fighting the browser. What we really should have done for our governments is figured out the 20 or so essential layouts and pre-coded CSS for them, but always allowed the government to fallback to custom HTML / CSS.
- Aeolun 8y agoNever mind that shifting one of them produces a cascade of changes that leads to some office worker spending a fruitful hour lining them all up again for version two...
- kqr 8y agoThis is one of the reasons I strongly prefer text-based/command-line interfaces: they're always scriptable. In the worst case you'll just generate a bunch of commands that'd take a human forever to execute.
- notahacker 8y agoThis. Documents are generally created and laid out for print and email distribution and often have very carefully laid out data tables, charts and page number referencing (as well as less important cosmetic formatting). Simply changing the file format isn't going to solve the accessibility problems and is going to create new formatting/compatibility issues, and and changing the workflow of every member of the civil service to require them to use an accessible HTML generation tool in place of word processors for anything that might be later made public isn't a trivial undertaking either. Said accessible HTML generation tool is probably going to want to change those nice HTML files back to PDF or Word files for restricted email distribution too...
- thanatropism 8y agoPandoc already exists, it's just difficult to use. You can write everything in Markdown and export to your org's Word template and have HTML, LaTeX, etc. export.
- tonyedgecombe 8y agoI really like markdown but I doubt it's the answer to this. These people aren't programmers, most of them will only have a loose grasp of what a file format is. What they need are tools that don't require a programming background.
- reaperducer 8y agoWell don't leave us in suspense, why isn't PDF a suitable replacement? Yes, but it's not a fully ACCESSIBLE document, which is half of the point of the article.
- jdietrich 8y agoHTML is easy. CSS is hard. CSS is hard partly because it's a mess, but mostly because designing for the web is hard. Normal human beings understand pages, in the papery sense of the word. They don't understand viewports. It takes an enormous leap of abstraction to reason about a document that could be any shape or size. Responsive design is a fundamentally unintuitive process. A lot of professional designers fail to understand this, even after years of designing for the web.
- Spivak 8y agoWell don't leave us in suspense, why isn't PDF a suitable replacement? * If your internal workflow is designing documents then the conversion to a web document will be clunky at best. * Every end-user device has a PDF reader and their web browser probably opens it transparently. * You need the PDF either way way because the website will never be the authoritative source so now you have the problem of making sure they don't get out of sync. * You probably have a few internal graphic designers that can do wonders with print but it's unlikely you have an internal web development team. * It's much easier to make a PDF accessible than a website. (Before you disagree remember that the offices we're talking about likely don't have a dedicated web designer) You can be sure it will print correctly, and for most users it's automatically offline.
- collyw 8y agoTrying to read a PDF on a mobile device is usually painful.
- thaumasiotes 8y agoSure, but that's because mobile devices have really small screens. You could create PDFs that were meant to be viewed at that size, but why? You'd have the same problem trying to read a regular book through a mobile-phone-sized window. That doesn't make books an unsuitable vehicle for document delivery.
- vidarh 8y agoIt does make it an unsuitable vehicle for delivery of information which people may want to access from a mobile device, however.
- thaumasiotes 8y agoNot at all; there is no information that people won't want to access from a mobile device. But again, a mobile device is not necessarily suitable for the job.