Re:HTML as an Accessible Format for Papers
by devnull3 on Saturday December 06, 2025 @12:15PM
(#46174901)
> HTML rendering requires you to be connected to the internet
Not really. One can always generate a self-contained html. Both CSS and JS (if needed) can be inline.
Re:HTML as an Accessible Format for Papers
by vatsachak on Saturday December 06, 2025 @01:33PM
(#46175492)
True but the webdev idiom is injecting things such as mathjax from a cdn. I guess one can pre-render the page and save that, but that's kind of like a PDF already
Re:HTML as an Accessible Format for Papers
by recursive on Saturday December 06, 2025 @12:16PM
(#46174910)
Why would html rendering require a network connection? It doesn't seem to on my machine.
Re:HTML as an Accessible Format for Papers
by vatsachak on Saturday December 06, 2025 @01:38PM
(#46175527)
Things like LaTeX equation rendering are hosted on a cdn
Re:HTML as an Accessible Format for Papers
by krapp on Saturday December 06, 2025 @01:46PM
(#46175598)
They can be but don't need to be. Any javascript can be localized like HTML and CSS.
Re:HTML as an Accessible Format for Papers
by vatsachak on Saturday December 06, 2025 @02:29PM
(#46175961)
That's fair, but imagine trying to get the average reader up to speed with something like npm.
Re:HTML as an Accessible Format for Papers
by krapp on Saturday December 06, 2025 @04:43PM
(#46176841)
You don't actually need npm either. You can literally just distribute everything - html, css, images and js in a zipped folder and open it locally.
Re:HTML as an Accessible Format for Papers
by nine_k on Saturday December 06, 2025 @12:35PM
(#46175059)
Try opening a PDF on a phone screen.
HTML rendering requires you to be connected to the internet, or setting up the images and mathJax locally. A PDF just works.
HTML obviously supports dynamic embedding, such as programs much better, but people just usually post a github.io page with the paper.