From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: PDF/UA Support
Date: Tue, 20 Oct 2015 09:06:02 +0200 [thread overview]
Message-ID: <5625E7DA.9030706@wxs.nl> (raw)
In-Reply-To: <20151019211110.3885627b@cea.fr>
On 10/20/2015 5:11 AM, Alan BRASLAU wrote:
> My understanding of PDF/UA is a very valid requirement to make texts
> accessible through standard tools, in particular but not limited to
> users having visual deficiencies, for example. This is the reason, not
> hype, behind the US government pushing this standard.
Sure, I understand that, but from what I've seen as demos I'm far from
convinced. If indeed that is the reason, then a better 'demand' would be
to provide several versions of the pdf (if rendering i.e. placement on
the page is important), for instance: b/w : for colorblind, large size
fonts, less fancy layouts etc .. in fact that would be an easy
requirement to meet.
The strange thing is that this tagged pdf standard does not have
provision to embed the whole source (in xml) and point to nodes, which
would be much more interesting (but not for publishers of course).
It just puzzles me why solutions for problems need to be complex. Or to
put it otherwise: if I had a disability I would consider this solution a
crappy poor mans one, not a real one.
> Alternative rendering (via web browsers, for example) will remain
> inferior for most uses as it will not benefit from much of what the TeX
> engine can produce, so this cannot really be the motivation.
It depends, providing an html file alongside even if it looks worse is
still better than some synthetic voice trying to make something of the
semi-structured content. In fact, I can imagine serious documents to
have proper audio embedded, done in a way that does justice to the problem.
Anyway ... we do support it, but on your bsd system: what viewer do you
use that supports it? We have tags for years and can't even test it
properly (ok, that has been the same for more pdf stuff).
> For reasons of Universal Accessibility, it would be a good idea for
> ConTeXt to indeed activate tagging by default. The argument of runtime
> and filesize (when proofing and in automatic workflows) is somewhat
> weak for one can ALWAYS deactivate this tagging for such cases. May I
> suggest that Hans reconsider his stand on this issue for the sake of
> promotion of ConTeXt as a very advanced typesetting tool.
our main own application of context is relative fast processing of
complex xml document and tagging is adding a lot of overhead
interesting is btw that pdf has all kind of compression and that has not
always influenced its design in a positive way, but with tagging the
file can become many times larger which is no fun (esp when one produces
huge pdf's then need to go over the web)
there are not many cases where in context we changed the default and
it's generally a bad idea as then one needs to go over all workflows and
en/disable things
of course the user can easily enable it on his system: just drop a
cont-loc.mkiv file in your texmf-local/tex/context/user path and enable
it there
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-10-20 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 15:50 Andrew Dunning
2015-10-19 21:33 ` Hans Hagen
2015-10-20 2:35 ` Andrew Dunning
2015-10-20 3:11 ` Alan BRASLAU
2015-10-20 7:06 ` Hans Hagen [this message]
2015-10-20 7:12 ` Hans Hagen
2015-10-20 13:26 ` Peter Rolf
2015-10-20 18:03 ` Andrew Dunning
2015-10-20 21:32 ` Peter Rolf
2015-10-20 21:38 ` Andrew Dunning
[not found] <mailman.1987.1445308552.2446.ntg-context@ntg.nl>
2015-10-20 8:07 ` Christoph Reller
2015-10-20 8:10 ` luigi scarso
2015-10-20 8:31 ` Hans Hagen
2015-10-20 13:37 ` Alan BRASLAU
2015-10-20 15:16 ` Hans Hagen
2015-10-20 8:48 ` Ulrike Fischer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5625E7DA.9030706@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).