ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: roadmap
Date: Tue, 15 May 2018 16:51:13 +0200	[thread overview]
Message-ID: <CAG5iGsB3MGccohczixbpvdAkjEjh0iPfbudRBgS=BgJ2F3Ht+w@mail.gmail.com> (raw)
In-Reply-To: <CAO8LnPGikYmhEeLOMG1znW4hUezL3-4dCZBQiWR2pr+NrfoV=A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1017 bytes --]

On Tue, May 15, 2018 at 4:46 PM, Christoph Reller <
christoph.reller@gmail.com> wrote:

> On Tue, 15 May 2018 08:23:04 +0200 luigi scarso <luigi.scarso@gmail.com>
> wrote:
>
>>
>> On Tue, May 15, 2018 at 8:15 AM, Christoph Reller <
>> christoph.reller@gmail.com> wrote:
>>
>> >
>> > 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.
>> >
>> What do you think of verapdf ?
>>
>
> Well, verapdf is only a validator and not a converter.
>
> And, by the way, there is no reasonable way to convert from, say, PDF/A-2b
> to PDF/A-2a without a rediculous amount of AI or manual input because the
> tagging cannot be created out of the blue. It has to be there from the
> document's birth. This is what makes this ConTeXt feature so precious.
>
> sure, the point is  if   verapdf  is reliable as validator.


-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2136 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

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

  reply	other threads:[~2018-05-15 14:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 14:46 roadmap Christoph Reller
2018-05-15 14:51 ` luigi scarso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-18  9:54 roadmap Christoph Reller
2018-05-15  6:15 roadmap Christoph Reller
2018-05-15  6:23 ` roadmap luigi scarso
2018-05-15  6:36 ` roadmap Hans Hagen
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='CAG5iGsB3MGccohczixbpvdAkjEjh0iPfbudRBgS=BgJ2F3Ht+w@mail.gmail.com' \
    --to=luigi.scarso@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).