ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andrew Dunning <andrew.dunning@utoronto.ca>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: PDF/UA Support
Date: Mon, 19 Oct 2015 22:35:46 -0400	[thread overview]
Message-ID: <02C4038A-A7D6-4FBB-9050-9D4B00BCDC33@utoronto.ca> (raw)
In-Reply-To: <562561B1.7000205@wxs.nl>


> On 19 Oct 2015, at 5:33 PM, Hans Hagen <pragma@wxs.nl> wrote:
> 
> Indeed context supports tagged pdf already for a while, although only acrobat can do something with it. Making it default is not really an option as there is overhead involved (a bit more runtime and much larger filesize) that makes no sense when proofing documents and in workflows for print, but enabling is easy with
> 
> \setuptagging[state=start]

Thank you! Would it also be possible to have something to the effect of `\setupbackend[format={pdf/ua:2014}` to set up the appropriate options?


> Btw, this feature relates to export to XML. Personally I wonder why this UA is such a hype, probably because publishers are reluctant to embed the document source in the pdf, which make much more sense when alternative rendering is needed.

I agree that I would prefer to see PDFs given alongside good HTML, but the reality is that this will not happen for some time to come, and in the meantime PDFs remain inaccessible to anyone with a print disability (and inconvenient for the rest of us). If we can improve this situation, it is only right that we do so. If we can in the process encourage wider adoption of ConTeXt, even better.

All best,

Andrew Dunning

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2015-10-20  2:35 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 [this message]
2015-10-20  3:11     ` Alan BRASLAU
2015-10-20  7:06       ` Hans Hagen
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=02C4038A-A7D6-4FBB-9050-9D4B00BCDC33@utoronto.ca \
    --to=andrew.dunning@utoronto.ca \
    --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).