From: Timothy <orgmode@tec.tecosaur.net>
To: emacs-orgmode@gnu.org
Cc: Jude DaShiell <jdashiel@panix.com>,
Timothy <orgmode@tec.tecosaur.net>,
Ihor Radchenko <yantar92@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: org exported pdf files
Date: Wed, 28 Sep 2022 17:19:52 +0800 [thread overview]
Message-ID: <877d1n3ky0.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <867d1nj1yn.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]
Hi Tim,
> It would probably be good to add the two above packages as part of the
> ’default’ package preamble, but this would require considerable testing
> as it isn’t known if there will be adverse effects when mixed with other
> packages.
Those packages are early accessibility experiments, and are /not/ intended for
wider use. See the top of the <https://github.com/AndyClifton/accessibility>
README: “Prototype. Not suitable for production”. The author themselves said in
a [2020 tex.SE answer] that:
`accessibility' was developed and published back in 2007 as a proof of concept for
some of the KOMA document styles. I got hold of the files from the author in
2019 and took over maintenance with her permission. I tidied up the package
enough to get it to CTAN, but didn’t update the functionality. I also published
it to GitHub to get some feedback on it.
It seems to have worked well in 2007 for a few test cases. Unfortunately it now
fails every test case, and it looks like needing some serious efforts to fix.
Because of this I no longer think that accessibility is fit for purpose.
They also go on to make a comment I’ve seen a few times from the people working
on the latex3 accessibility project — basically that in order to actually get
a /good/ solution, we’ll need to wait till support is baked into the LaTeX core.
If we’re desperate to add this, we’ll likely want to look at `tagpdf' which is
written by someone working on the latex3 accessibility project. It is apparently
capable of passing PCA3, however according to the author:
`tagpdf' hasn’t been written as a user package but to allow experiments and tests
and to help to identify missing interfaces in the kernel and in packages. It can
change at any time in incompatible ways and it requires some skills to use it.
So, while it may be a particularly boring answer, I think “wait and see” is our
current best bet.
All the best,
Timothy
[2020 tex.SE answer] <https://tex.stackexchange.com/a/551287/167605>
next prev parent reply other threads:[~2022-09-28 12:45 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 [this message]
2022-09-28 17:08 ` Tim Cross
2022-09-28 17:39 ` Timothy
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=877d1n3ky0.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).