From: Rasmus <email@example.com>
Subject: Re: pdf screen reader accessibility?
Date: Mon, 06 Apr 2015 15:19:32 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Marcin Borkowski <email@example.com> writes:
> On 2015-04-06, at 13:40, Rasmus <firstname.lastname@example.org> wrote:
>> Jude DaShiell <email@example.com> writes:
>>> is a good place to start.
>> It's a list of a bunch of software packages of which most are not (i) free
>> in any meaning of the word; and (ii) supported on GNU/Linux.
> So what? IIUC, the OP wants to have something similar using Emacs and
> (maybe) free (in a usual sense, or in FSF sense) software. Isn't it
> a valid request?
Of course it is, but OP is referring to features of some software that I
don't have access to, so how am I supposed to make sense of it? I'm not
going to (i) install a new OS; and (ii) buy/torrent software to understand
and test a feature in named software.
If there's a standard I'm eager to hear about it.
> Maybe it's an answer to my question below?
> | > Do those files by default conform to screen reader accessibility standards
> | > or can such files be made to conform to screen reader accessibility
> | > standards? Since adobe was responsible for creating pdf files Adobe has
> | > screen reader accessibility standards on its website.
> | Could you point out these standards (direct links)?
> (No idea why the OP started a new thread, though.) In my browser, on
> the right there are some links to general accessibility info (or so it
> seems, I didn't follow them yet).
>>> When a document gets written in Microsoft Word, its language is made
>>> part of that document. If that document is later converted to a pdf
>>> file that language information is taken in by the conversion process
>>> then becomes the first component that starts to make screen reader
>>> accessibility of a pdf file possible.
>> AFAIK, the language is set as part of the metadata in pdfs in 8.3 based
>> on #+LANGUAGE. Can you test if that works for you? If not, what will
>> needed to be changed to make it work?
> Quick test using
> #+LANGUAGE: polish
> #+LANGUAGE: pl
> showed it didn't work. (I didn't check the pdf file, though, only
> grepped the LaTeX source.)
Please give an example of how to specify the language, or an example of a
way to test it that can be done easily from GNU/Linux.
With emacs -q and Org 8.3, and a document with "#+LANGUAGE: da" I get:
$> exiftool test.pdf | grep -i lang
Language : Danish
Send from my Emacs
next prev parent reply other threads:[~2015-04-06 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 8:25 pdf screen reader accessibility? Jude DaShiell
2015-04-06 11:40 ` Rasmus
2015-04-06 12:39 ` Marcin Borkowski
2015-04-06 13:19 ` Rasmus [this message]
2015-04-08 18:22 ` William Henney
2015-04-08 18:48 ` Rasmus
2015-04-08 20:22 ` Nick Dokos
2015-04-08 20:27 ` Rasmus
2015-04-08 21:07 ` Helm and multiple-tags in org mode issues Leo Ufimtsev
2015-04-08 21:48 ` pdf screen reader accessibility? Nick Dokos
2015-04-07 7:49 Jude DaShiell
2015-04-07 8:12 ` Rasmus
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).