From: Peter Rolf <indiego@gmx.net>
To: ntg-context@ntg.nl
Subject: Re: PDF/A-3a attachment support query
Date: Sat, 7 Dec 2019 15:09:35 +0100 [thread overview]
Message-ID: <6b718eed-2345-8c43-4756-6d2a2c3c73ca@gmx.net> (raw)
In-Reply-To: <6a2b9bbf-d820-fe23-bf80-246bb7bee8fa@xs4all.nl>
Am 06.12.2019 um 16:56 schrieb Hans Hagen:
> On 12/6/2019 4:21 PM, Peter Rolf wrote:
>> Hi Rik,
>>
>> I guess it's not supported yet.
>>
>> In "lpdf-fmt.lua" it says:
>> [..]
>> ["pdf/a-3a"] = { -- untested; NEW: any type of attachment is
>> allowed
>> [..]
>>
>> I remember adding the "a-2a" and "a-3a" versions back when Hans and I
>> added experimental support for "PDF/UA-1" (which is based on "PDF/A-3a",
>> but much more limited). This all lies back a few years, can't remember
>> the details.
>>
>> So we have only basic support for "PDF/A-3a", the more advanced features
>> of that format are not supported yet. The main problem here is the
>> lacking PDF/A documentation (ISO pay wall). I guess there is currently
>> no real reason to use that format at all (?).
> indeed (and to be honest, i never need these options myself)
>
> anyway, i happily wait till you come up with an entry for it
>
> (i have no clue what 'advanced' features mean here, something we need to
> implement or just something that needs a flag)
>
@Hans:
I'll look into it. Give me some days to read the documentation (not that
much anyway) and to play around with it.
All the "new" features are already implemented as building blocks for
the PDF/X variants, so I guess it's mostly just adding some new table
entries ('b|u' variants). Attachments seem to need several extra PDF
entries. Will report back to you and Luigi.
@Luigi: mh, that really looks like a lot of fun
https://docs.verapdf.org/validation/pdfa-parts-2-and-3/
@Pablo, Rik:
We can put you in cc if you volunteer for testing. Just say aye :D
Peter
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-12-07 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 2:11 Rik Kabel
2019-12-06 15:21 ` Peter Rolf
2019-12-06 15:37 ` luigi scarso
2019-12-06 15:56 ` Hans Hagen
2019-12-07 14:09 ` Peter Rolf [this message]
2019-12-06 17:08 ` Pablo Rodriguez
2019-12-07 13:21 ` Pablo Rodriguez
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=6b718eed-2345-8c43-4756-6d2a2c3c73ca@gmx.net \
--to=indiego@gmx.net \
--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).