From: "T.V Raman" <raman@google.com>
To: manikulin@gmail.com
Cc: raman@google.com, emacs-orgmode@gnu.org
Subject: Re: Org mode export accessibility
Date: Fri, 30 Sep 2022 06:29:14 -0700 [thread overview]
Message-ID: <25398.61226.614726.254480@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <bbe296a1-5424-d19b-45fe-76bbe75a9be3@gmail.com>
As one example, yes.
Here is hopefully a more detailed explanation:
1. First off, here Accessibility == Specifically, Accessibility to the
blind.
2. For blind and low vision users, you may need to "re-render" the
math, either via magnification, speech or Braille.
3. For doing this, you need the original "generating markup" MathML,
or better yet LaTeX (those distinctions require more explanation,
but this should suffice for this thread)
4. When things are rendered to PDF, a derivative format that traces
back to the print world and traditionally didn't feel the need to
recreate the original, all that info from (3) is lost.
5. For regular document structure, e.g. headings etc, PDF now supports
this "natively" via something called "marked content" introduced in
the late 90's; to leverage this, publishing tools exporting to PDF
can leverage that facility to enable downstream tools re-create or
extract an approximation of the original structure.
6. The above left out Math --- mostly because authoring tools did not
go as far as doing that for Math.
7. Then you got pdftex that replaced DVI (which was essentially pure
visual layout) with PDF -- also pure visual layout -- but a format
that has continued to evolve.
8. Now, connect the dots, newer LaTeX packages like the one mentioned
(there may well be others now or in the future) can inprinciple
ensure that the required "back pointers to regenerate the original
markup" can make it all the way through to the generated PDF.
9. Note that this is not the end of the trail; for such exports to
make a difference to the end-user, user-facing tools still need to
know "how" to leverage these facilities.
Max Nikulin writes:
> Accessibility issues of exported files have been raised on the Org mode
> mail list again. I decided to revive this thread because I noticed a
> LaTeX package that may be related to the following suggestion (I am not
> sure that I got it right though).
>
> On 07/07/2022 21:42, T.V Raman wrote:
> >
> > 3. For math especially, make sure the TeX/LaTeX is preserved one
> > way or the other in the export
>
> Math can be extracted from PDF files as TeX commands using e.g.
> pdftotext if LaTeX source file contains \usepackage{mmap}. Is it what
> you were writing about?
>
> https://ctan.org/pkg/mmap
> https://mirrors.ctan.org/macros/latex/contrib/mmap/README
>
> The latest thread with discussion of accessibility:
>
> https://list.orgmode.org/th4dth$5df$1@ciao.gmane.io
> Max Nikulin Re: Add \usepackage{cmap} as default LaTeX class in ox-latex
> (was: org exported pdf files) Thu, 29 Sep 2022 22:34:07 +0700.
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
next prev parent reply other threads:[~2022-09-30 13:31 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 14:30 About 'inline special blocks' Juan Manuel Macías
2022-05-23 15:20 ` Kaushal Modi
2022-05-23 21:06 ` Juan Manuel Macías
2022-05-24 2:36 ` Tim Cross
2022-05-24 2:51 ` Timothy
2022-05-24 6:54 ` Eric S Fraga
2022-05-26 7:30 ` Christian Moe
2022-05-24 15:09 ` Max Nikulin
2022-05-25 7:22 ` Ihor Radchenko
2022-05-25 17:05 ` Max Nikulin
2022-05-26 2:54 ` Merging paragraphs separated by comment lines during export (was: About 'inline special blocks') Ihor Radchenko
2022-05-24 3:56 ` About 'inline special blocks' Ihor Radchenko
2022-05-24 14:05 ` João Pedro
2022-05-26 4:56 ` Ihor Radchenko
2022-05-26 11:30 ` João Pedro
2022-05-26 12:20 ` Ihor Radchenko
2022-05-26 17:35 ` João Pedro
2022-05-26 21:22 ` About opening issues vs email [Was: About 'inline special blocks'] Kaushal Modi
2022-05-27 4:24 ` Ihor Radchenko
2022-05-27 4:36 ` João Pedro
2022-05-25 13:55 ` About 'inline special blocks' Juan Manuel Macías
2022-06-17 6:28 ` Ihor Radchenko
2022-06-17 19:49 ` Juan Manuel Macías
2022-06-19 12:47 ` Juan Manuel Macías
2022-06-19 19:30 ` Christian Moe
2022-06-19 20:15 ` Juan Manuel Macías
2022-06-19 22:18 ` Tim Cross
2022-06-20 16:57 ` Max Nikulin
2022-06-20 19:06 ` Juan Manuel Macías
2022-06-21 16:39 ` Max Nikulin
2022-06-21 18:19 ` Juan Manuel Macías
2022-06-20 22:46 ` Tim Cross
2022-06-26 4:07 ` Org mode export accessibility (was: About 'inline special blocks') Ihor Radchenko
2022-06-26 6:29 ` Tim Cross
2022-06-26 10:46 ` Org mode export accessibility Juan Manuel Macías
2022-06-26 10:54 ` Ihor Radchenko
2022-06-27 14:40 ` T.V Raman
2022-06-30 7:53 ` Ihor Radchenko
2022-07-07 14:18 ` briangpowell
2022-07-07 14:42 ` T.V Raman
2022-07-08 4:38 ` Ihor Radchenko
2022-07-08 13:55 ` T.V Raman
2022-07-09 3:39 ` Ihor Radchenko
2022-07-09 13:20 ` T.V Raman
2022-09-30 11:07 ` Max Nikulin
2022-09-30 13:29 ` T.V Raman [this message]
2022-09-30 16:43 ` Max Nikulin
2022-09-30 16:55 ` T.V Raman
2022-10-01 4:36 ` Ihor Radchenko
2022-10-01 14:59 ` T.V Raman
2022-10-02 2:54 ` Org source in PDF (Re: Org mode export accessibility) Max Nikulin
2022-10-02 3:50 ` Timothy
2022-07-07 14:43 ` Org mode export accessibility T.V Raman
2022-07-07 15:37 ` T.V Raman
2022-07-08 4:33 ` Ihor Radchenko
2022-07-08 13:54 ` T.V Raman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25398.61226.614726.254480@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).