From: Timothy <orgmode@tec.tecosaur.net>
To: emacs-orgmode@gnu.org
Cc: Timothy <orgmode@tec.tecosaur.net>,
Jude DaShiell <jdashiel@panix.com>,
Ihor Radchenko <yantar92@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: org exported pdf files
Date: Thu, 29 Sep 2022 01:39:08 +0800 [thread overview]
Message-ID: <875yh72y3n.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <86tu4ro11c.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
Hi Tim,
> None of what yuo wrote is a surprise. Unfortunately, it does mean two
> things
>
> 1. Org mode cannot be used to create accessible PDF documents as long as
> it depends on the latex environment to generate those documents.
It means that Org mode cannot /currently/ be used…
I have hope that in 1-2y this will change.
> 2. Technically, Org mode cannot be used in any organisation (specifically government
Can’t comment on this.
> I don’t know if other document processors, like perhaps pandoc, can
> create PDF files which contain the tagging and other structural
> metadatra necessary to make PDFs accessible.
Pandoc’s PDFs via LaTeX will have exactly the same problem.
> Note that org also lacks any accessibility support for HTML generated
> documents as well. However, this is less problematic as authors do have
> some ability to add the necessary attributes that can improve
> accessibility - an option not available with Latex.
HTML has more inherent structure, so this situation is already much better.
> An unfortunate situation really - especially given Emacs has one of the
> most powerful and advanced accessibility options available via
> emacspeak.
Well, Emacs is a bit divorced from this problem.
> I also won’t hold my breath for a new latgex core. THe latex3 initiative
> seems to have failed or at least appears to be slower to be realised than perl6!
Hmm? LaTeX3 switched gear, and arguably is working nicely. I expect you’re
currently using quite a few bits of LaTeX3, even if you don’t know it.
The accessibility effort was started ~2y ago, seems to be making progress
(stalled a bit with covid), and is funded with a roadmap. I see good reason to
think the current situation will change.
All the best,
Timothy
next prev parent reply other threads:[~2022-09-28 18:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 1:48 org exported pdf files Jude DaShiell
2022-09-27 2:48 ` Ihor Radchenko
2022-09-27 3:15 ` Jude DaShiell
2022-09-27 3:24 ` Ihor Radchenko
2022-09-27 4:31 ` Jude DaShiell
2022-09-27 4:58 ` Ihor Radchenko
2022-09-28 4:36 ` Jude DaShiell
2022-09-28 4:53 ` Timothy
2022-09-28 6:48 ` Jude DaShiell
2022-09-28 8:47 ` Tim Cross
2022-09-28 9:19 ` Timothy
2022-09-28 17:08 ` Tim Cross
2022-09-28 17:39 ` Timothy [this message]
2022-09-28 18:23 ` Juan Manuel Macías
2022-09-29 20:58 ` Tim Cross
2022-09-29 4:09 ` Org HTML export accessibility (was: org exported pdf files) Ihor Radchenko
2022-09-29 8:22 ` Tim Cross
2022-09-29 11:43 ` Jude DaShiell
2022-09-29 21:05 ` Apology [was: Re: Org HTML export accessibility (was: org exported pdf files)) Tim Cross
2022-09-30 5:34 ` tomas
2022-10-02 10:59 ` Apology [ Fraga, Eric
2022-10-02 9:42 ` [HELP] Help implementing org-lint/warnings buffer during export (was: Org HTML export accessibility (was: org exported pdf files)) Ihor Radchenko
2022-10-02 20:52 ` Tim Cross
2022-10-03 3:25 ` Ihor Radchenko
2022-09-29 7:07 ` org exported pdf files Max Nikulin
2022-09-29 21:00 ` Tim Cross
2022-10-01 10:55 ` Max Nikulin
2022-09-28 13:02 ` Jude DaShiell
2022-09-28 16:12 ` Max Nikulin
2022-09-27 11:08 ` Max Nikulin
2022-09-28 3:07 ` Ihor Radchenko
2022-09-28 15:58 ` Max Nikulin
2022-09-29 4:12 ` Add \usepackage{cmap} as default LaTeX class in ox-latex (was: org exported pdf files) Ihor Radchenko
2022-09-29 15:34 ` Max Nikulin
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=875yh72y3n.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=emacs-orgmode@gnu.org \
--cc=jdashiel@panix.com \
--cc=yantar92@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).