by rmbeard on 9/11/20, 4:27 PM with 74 comments
by choeger on 9/11/20, 7:48 PM
There is no good reason to put the accessibility into the type setting. Instead, use a declarative (e.g., any markup) language, translate that a) to (LaTeX) and b) to accessibility annotations and then combine the two results. Problem solved.
Unfortunately you will either lose a lot of expressiveness along the way or you have to find a very sophisticated markup language.
by hprotagonist on 9/11/20, 5:43 PM
This comes up a bit around the blind accessibility issue for mathematics, which is why I suspect it's bubbling up this week on HN.
by scoresmoke on 9/11/20, 6:59 PM
- https://ctan.org/pkg/accessibility
I am using the former for some personal documents and found that it improves text selection and copying on Apple devices. (This could be related to how PDFKit handles text.)
Edit: formatting.
by bfirsh on 9/11/20, 7:41 PM
It's 80% of the way there, but with 80% more work it could be a pretty complete implementation.
It powers this: https://www.arxiv-vanity.com/
by vehemenz on 9/11/20, 6:13 PM
by ffk on 9/11/20, 5:47 PM
[edit to add link to pandoc]
by minikites on 9/11/20, 7:01 PM
by bokumo on 9/11/20, 6:43 PM
by amai on 9/18/20, 9:22 AM
"Did I mention that both Word and LibreOffice generate tagged PDFs?"
But then the simple solution is this: Convert your LaTeX to Word or LibreOffice. Then generate the PDF.
Absurdly the easiest way to convert LaTeX to Word/LibreOffice is by creating a PDF first (https://tex.stackexchange.com/questions/111886/how-to-conver...), import that into Word/LibreOffice and then create your PDF/A from that.
by hugh-avherald on 9/11/20, 6:01 PM
by mci on 9/11/20, 6:44 PM
2. Even by 2016, pdfTeX had been largely superseded by LuaTeX.
3. The author bizzarely links to "the mess" of the literate source of TeX the program as a WEB file rather than as a typeset document.
4. AIUI, the source code of the TeX engine has nothing/very little to do with adding tags to PDFs, which it is the job for LaTeX packages. Admittedly, understanding and writing their source code is a rarer skill than reading the literate source of TeX.
by amai on 9/18/20, 9:31 AM
by aklemm on 9/11/20, 6:21 PM
by konjin on 9/11/20, 5:47 PM
Yes, you literally read the literate program of TeX and understand what's going on: http://brokestream.com/tex.pdf
I had never learned Pascal but I've managed to edit and compile TeX successfully, and it was easier than trying to understand any of my own non-literate programs.
>My point being that if we wouldn’t rely on TeX itself and use ANT (or whatever alternative) which is written in the quite elegant OCaml, than hacking it would be at least possible for mere mortals. Although I have to admit, despite being in love with OCaml since my PhD days, it’s also a quite niche language. But imagine if the whole thing was written in Python, or at least C.
Imagine if software engineers were actual engineers instead of glorified script kiddies.
>I wish someone would design a new space shuttle because while it's a neat project I only understand MKS units and it's too much effort to use a calculator for converting between them and Imperial units.
by rbobby on 9/11/20, 5:56 PM
Revisit this comment in 5 years.
by svnpenn on 9/11/20, 5:55 PM
https://github.com/dompdf/dompdf
Need a page break? Here you go:
https://developer.mozilla.org/Web/CSS/break-after
Im not sure what you would do about TikZ and stuff like this, but I have seen some pretty wild stuff in CSS, so surely its possible: