Drop files here Tap to add files.
UK creates would be a first step. UK has features to track versions of HTML content, through the 'page history' at the foot of each page which includes notes about what has changed. They generally require a lot of zooming in and out, and scrolling both vertically and horizontally. Which might not be a problem if it promised backwards compatibility, but it does not, and HTML features from previous versions have already been deprecated and browsers advise can be obseleted at any pont.
Comment by Nathan Dolan posted on on 18 July 2018.
However, the downside is that there will be people who do not or cannot access the content. You can read the 33 responses here: PDFreactor supports cgroup based virtualization environments like Docker.
They share the concerns that Nathan raised above that "HTML is not in any way a long-term archival format. Large text is easier to read, but does require more scrolling.
UK threw away when it erased businesslink. Comment by Gemma posted on on 20 July 2018. Many of your arguments for html seem to be based on your own needs for data and analysis. Locking content into a PDF limits the ability for people to make these kind of accessibility customisations. Looking towards the EU directive, it would be great to post as html, but there is no option for this on the production site - the only option is to upload a new file.
Comment by Neil Williams posted on on 07 August 2018. Any subscript and superscript formatting is also stripped.
It is helpful for the understanding of HTML5 tags and after study about this sheet. Sometimes they automatically download to the user's device. HTML is great for but sucks for documents.
Comment by Roger posted on on 18 July 2018 Excellent post Neil and I agree with you about the 'ingrained print culture and outdated content production processes. In a PDF-free world!
We cannot get as much information from analytics about how people are using PDFs. Comment by Abdurrehman posted on on 16 July 2018 I think there's still a lot to cover our final destination is not pdf or html its to be machine readable in the context of web 2.
Just as long as you leave the ability to consolidate all the many and various chapters of the huge documents that you are publishing this way into a single version for someone who still likes to read a BOOK. Similarly, users cannot use browser extensions and add-ons such as Google translate on PDF content.