LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Tue, 7 Sep 2021 17:22:37 +0100
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
MIME-Version:
1.0
Message-ID:
In-Reply-To:
Content-Type:
multipart/alternative; boundary="00000000000035717f05cb6a2d59"
From:
Jonathan Fine <[log in to unmask]>
Parts/Attachments:
text/plain (2518 bytes) , text/html (3885 bytes)
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


ATOM RSS1 RSS2