ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Christoph Reller <christoph.reller@gmail.com>
Subject: Re: roadmap
Date: Tue, 15 May 2018 08:36:46 +0200	[thread overview]
Message-ID: <8d41bd35-d3c2-da04-996e-c02ae792aa42@xs4all.nl> (raw)
In-Reply-To: <CAO8LnPG3ZGdJVrMqcvnWrwC-gZ91kBTxcDo3h=O4wsoT1SZtTA@mail.gmail.com>

On 5/15/2018 8:15 AM, Christoph Reller wrote:
> On Tue, May 15, 2018 at 12:53 AM, <ntg-context-request@ntg.nl> wrote:
>>
>>
>> Message: 3
>> Date: Mon, 14 May 2018 23:26:28 +0200
>> From: Hans Hagen <j.hagen@xs4all.nl>
>> To: Henning Hraban Ramm <texml@fiee.net>, mailing list for ConTeXt
>>          users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] roadmap
>> Message-ID: <c504ea08-a021-4444-4eba-c2894d72da52@xs4all.nl>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> On 5/14/2018 9:36 PM, Henning Hraban Ramm wrote:
>>> Hi Hans, thank you so much!
> 
> Keep up the good work!
> 
>>> * PDF/* (X, A, UA - probably only reasonable with external tools, but it seems like there’s not a lot that’s usable)
>>
>> we support various formats (to some extend the backend even adapts to
>> it) ... tagged pdf ... already there for quite a while but i never had
>> any demand for it so i never really check the current state (also
>> because imo it's a it weird feature ... only there because publishers
>> don't want to distribute sources that are suitable for rendering
>> variations ... so we're stuck with some pseudo structure related to
>> visuals)
>>
>> (i might upgrade tagging and exports as they closely relate but it's not
>> easy to get motivated for something that one has no real use for so at
>> most it will cold winter evening stuff)
> 
> To us, tagged PDF is important. Specifically, for PDF/A with
> compliance level a, tagging is mandatory. ConTeXt is the only (!)
> TeX-based PDF creation suite that can produce correct and reliable
> tagging.
> 
> Our company is producing (and weekly updating) 67 manuals and
> technical documents from more than 900 ConTeXt source files for our
> software products. The output PDFs are converted to PDF/A-2a, which is
> only possible due to ConTeXt's tagging.
> 
>  From what we hear of our customers, PDF/A level a and PDF/UA are
> becoming increasingly important, be it because of archiving issues or
> because of legislation requirements. So please, maintain this
> invaluable feature!
Ah, it's good to hear that it's working ok. (Of course it is/will be 
maintained ... it's just that because I don't need it myself it's up to 
folks like you to check if it's ok.)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2018-05-15  6:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15  6:15 roadmap Christoph Reller
2018-05-15  6:23 ` roadmap luigi scarso
2018-05-15  6:36 ` Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-18  9:54 roadmap Christoph Reller
2018-05-15 14:46 roadmap Christoph Reller
2018-05-15 14:51 ` roadmap luigi scarso
2018-05-14 15:17 roadmap Hans Hagen
2018-05-14 19:36 ` roadmap Henning Hraban Ramm
2018-05-14 21:26   ` roadmap Hans Hagen
2018-05-15  9:01     ` roadmap MF
2018-05-14 22:52 ` roadmap Henri Menke
2018-05-14 23:34   ` roadmap Hans Hagen
2018-05-16  5:38     ` roadmap Henri Menke
2018-05-16  6:24       ` roadmap Joseph Canedo
2018-05-16  7:28       ` roadmap Hans Hagen
2018-05-14 23:41   ` roadmap luigi scarso
2018-05-15 19:17 ` roadmap Pablo Rodriguez
2018-05-15 21:26   ` roadmap Hans Hagen
2018-05-16 15:18     ` roadmap Pablo Rodriguez
2018-05-16 19:14 ` roadmap Fabrice L
2018-05-17 13:06   ` roadmap Hans Hagen
2018-05-17 14:24     ` roadmap Mohammad Hossein Bateni
2018-05-17 15:47       ` roadmap Otared Kavian
2018-05-17 16:50         ` roadmap Hans Hagen

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=8d41bd35-d3c2-da04-996e-c02ae792aa42@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=christoph.reller@gmail.com \
    --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).