Thur 9 Sept: TeX Hour: Rich DVI files and accessible PDF (6:30 to 7:30pm UK time)
Jonathan Fine <[email protected]> Tue, 7 Sep 2021 17:22:37 +0100
| Newsgroups | gmane.comp.tex.latex.latex3 |
|---|---|
| Message-ID | <CALD=Yf-1Z0_Kgddnd0G3Bzu56WOSEXOvBq+Jzv6Jsu6uUer5HQ@mail.gmail.com> |
--00000000000035717f05cb6a2d59 Content-Type: text/plain; charset="UTF-8" Hi Summary: TeX converts source to DVI, an abstract page description language. By definition, a rich DVI file contains word-by-word backlinks to the TeX source. We discuss how to create rich DVI, and how to render it to an accessible PDF. We compare this to the LaTeX Project approach. Date and time: Thursday 9 September, 6.30 to 7.30pm UK time. UK time now: https://time.is/UK. Zoom URL: https://us02web.zoom.us/j/78551255396?pwd=cHdJN0pTTXRlRCtSd1lCTHpuWmNIUT09 OVERVIEW Producing accessible PDF from LaTeX source would be a tremendous advance (as would reliable production of accessible HTML). A large part of the problem of creating accessible PDFs is to merge two document trees, namely the TeX source (as HTML) and the PDF. At last month's TeX Conference Frank Mittlebach presented his solution to this problem. At tomorrow's TeX Hour I'll present my solution, via the concept of rich DVI files. This goes back 25 years, to my TUGBoat article "Editing .dvi Files, or Visual TEX". Although in some ways dated, the basic concepts are still sound and even more relevant than before. My approach is to pre-process the source tree so that every word (and similar source objects) is tagged in the resulting DVI file. This will then give a rich DVI, from which an external program can create an accessible PDF. Frank's approach is similar, except that he uses complex and ingenious LaTeX macros for everything, and tags only the paragraphs. Frank's approach leads to a multi-year journey to modernize LaTeX, and avoids the need for a post-processor. My approach can use current LaTeX, by use of an input filter to add tagging, and an output filter to render the rich DVI to accessible PDF. This is an important choice, which will affect TeX for over 30 years. If you're keen, you can read about these two approaches at https://tug.org/TUGboat/tb17-3/tb52finv.pdf https://tug.org/tug2021/assets/pdf/Frank-Mittelbach-slides.pdf INVITE You're invited to tomorrow's TeX Hour: Rich DVI files and accessible PDF. Date and time: Thursday 9 September, 6.30 to 7.30pm UK time. UK time now: https://time.is/UK. Zoom URL: https://us02web.zoom.us/j/78551255396?pwd=cHdJN0pTTXRlRCtSd1lCTHpuWmNIUT09 Meeting ID: 785 5125 5396 Passcode: knuth LAST WEEK'S VIDEOS Last week's TeX Hour was on Docs and help for LaTeX users. The videos are available at https://www.youtube.com/playlist?list=PLw1FZfIX1w7h74asldt29nO1XUiNrWSnz Arising from that is a project to help users find existing advice on LaTeX best practice, https://github.com/texhour/latex-best-practice Happy TeXing Jonathan --00000000000035717f05cb6a2d59 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><div class=3D"= gmail_quote"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">H= i<br><br>Summary: TeX converts source to DVI, an abstract page description = language. By definition, a rich DVI file contains word-by-word backlinks to= the TeX source. We discuss how to create rich DVI, and how to render it to= an accessible PDF. We compare=C2=A0this to the LaTeX Project approach.<br>= <br>Date and time: Thursday 9 September, 6.30 to 7.30pm UK time.<br>UK time= now: <a href=3D"https://time.is/UK" target=3D"_blank">https://time.is/UK</= a>.<br>Zoom URL: <a href=3D"https://us02web.zoom.us/j/78551255396?pwd=3DcHd= JN0pTTXRlRCtSd1lCTHpuWmNIUT09" target=3D"_blank">https://us02web.zoom.us/j/= 78551255396?pwd=3DcHdJN0pTTXRlRCtSd1lCTHpuWmNIUT09</a><br><br>OVERVIEW<div>= Producing accessible PDF from LaTeX source would be a tremendous advance (a= s would reliable production of accessible HTML).=C2=A0A large part of the p= roblem of creating accessible PDFs is to merge two document trees, namely t= he TeX source (as HTML) and the PDF.=C2=A0 At last month's TeX Conferen= ce Frank Mittlebach presented his solution to this problem.</div><div><br><= /div><div>At tomorrow's TeX Hour I'll present my solution, via the = concept of rich DVI files. This goes back 25 years, to my=C2=A0TUGBoat arti= cle "Editing .dvi Files, or Visual TEX". Although in some ways da= ted, the basic concepts are still sound and even more relevant than before.= <div><div><br></div><div>My approach is to pre-process the source tree so t= hat every word (and similar source objects) is tagged in the resulting DVI = file. This will then give a rich DVI, from which an external program can cr= eate an accessible PDF. Frank's approach is similar, except that he use= s complex and ingenious LaTeX macros for everything, and tags only the para= graphs.<br></div><div><br></div><div>Frank's approach leads to a multi-= year journey to modernize LaTeX, and avoids the need for a post-processor. = My approach can use current LaTeX, by use of an input filter to add tagging= , and an output filter to render the rich DVI to accessible PDF.</div><div>= <br></div><div>This is an important choice, which will affect TeX for over = 30 years. If you're keen, you can read about these=C2=A0two approaches = at</div><div><a href=3D"https://tug.org/TUGboat/tb17-3/tb52finv.pdf" target= =3D"_blank">https://tug.org/TUGboat/tb17-3/tb52finv.pdf</a></div><div><a hr= ef=3D"https://tug.org/tug2021/assets/pdf/Frank-Mittelbach-slides.pdf" targe= t=3D"_blank">https://tug.org/tug2021/assets/pdf/Frank-Mittelbach-slides.pdf= </a><br></div><div><br>INVITE<br>You're invited to tomorrow's TeX H= our: Rich DVI files and accessible PDF.<br>Date and time: Thursday 9 Septem= ber, 6.30 to 7.30pm UK time.<br>UK time now: <a href=3D"https://time.is/UK"= target=3D"_blank">https://time.is/UK</a>.<br>Zoom URL: <a href=3D"https://= us02web.zoom.us/j/78551255396?pwd=3DcHdJN0pTTXRlRCtSd1lCTHpuWmNIUT09" targe= t=3D"_blank">https://us02web.zoom.us/j/78551255396?pwd=3DcHdJN0pTTXRlRCtSd1= lCTHpuWmNIUT09</a><br>Meeting ID: 785 5125 5396<br>Passcode: knuth<br><br>L= AST WEEK'S VIDEOS<br>Last week's TeX Hour was on Docs and help for = LaTeX users.=C2=A0 The videos are available at=C2=A0<a href=3D"https://www.= youtube.com/playlist?list=3DPLw1FZfIX1w7h74asldt29nO1XUiNrWSnz" target=3D"_= blank">https://www.youtube.com/playlist?list=3DPLw1FZfIX1w7h74asldt29nO1XUi= NrWSnz</a></div><div><br></div><div>Arising from that is a project=C2=A0to = help users find existing advice on LaTeX best practice,</div><div><a href= =3D"https://github.com/texhour/latex-best-practice" target=3D"_blank">https= ://github.com/texhour/latex-best-practice</a><br><br>Happy TeXing<br></div>= </div><div><br></div><div>Jonathan</div></div></div> </div></div> </div></div> </div></div> --00000000000035717f05cb6a2d59--