Re: [dev-context] /MarkInfo refers to empty object

On 10/23/2017 10:07 PM, Pablo Rodriguez wrote: On 10/23/2017 09:53 PM, Hans Hagen wrote: On 10/23/2017 8:40 PM, Pablo Rodriguez wrote: [...] to the new content in beta 2017.10.19 13:50: Marked= lpdf.majorversion == 1 and pdfboolean(true) or nil, for now change that to

Re: [dev-context] fix output intent subtype

On 10/23/2017 11:14 PM, Peter Rolf wrote: Am 23.10.2017 um 19:14 schrieb Hans Hagen: On 10/23/2017 7:01 PM, luigi scarso wrote: On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez wrote: Hans, according to Boris Doubrov (one of the developers of the veraPDF parser for PDF/A

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 9:15 AM, Hans Hagen wrote: > > Well, for me it means that all that validation esp of keys like this are > rather useless (creating work) because docs validated in the past and > archived now are suddenly no longer valid. Hm I have made a pdf with

Re: [dev-context] fix output intent subtype

Am 24.10.2017 um 09:15 schrieb Hans Hagen: > On 10/23/2017 11:14 PM, Peter Rolf wrote: >> Am 23.10.2017 um 19:14 schrieb Hans Hagen: >>> On 10/23/2017 7:01 PM, luigi scarso wrote: On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez wrote: > Hans, > > according to Boris

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 10:01 AM, Peter Rolf wrote: > > Yes. My guess (as I have no ISO documention) at that time was, that the > number should be increased with the versions. I couldn't imagine, why > the should use a number in that flag (there may be reasons for it, but I >

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 10:14 AM, luigi scarso wrote: > On Tue, Oct 24, 2017 at 10:01 AM, Peter Rolf wrote: >> >> Yes. My guess (as I have no ISO documention) at that time was, that the >> number should be increased with the versions. I couldn't

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 10:23 AM, luigi scarso wrote: > On Tue, Oct 24, 2017 at 10:14 AM, luigi scarso wrote: > infact > $ convert cow-brown.pdf --flatten -density 300 cow-brown.png > > > %% unrgb.tex > \nopdfcompression >

Re: [dev-context] fix output intent subtype

Am 24.10.2017 um 10:01 schrieb Peter Rolf: > Am 24.10.2017 um 09:15 schrieb Hans Hagen: >> On 10/23/2017 11:14 PM, Peter Rolf wrote: >>> Am 23.10.2017 um 19:14 schrieb Hans Hagen: On 10/23/2017 7:01 PM, luigi scarso wrote: > On Mon, Oct 23, 2017 at 6:25 PM, Pablo Rodriguez

Re: [dev-context] fix output intent subtype

On 10/24/2017 09:49 AM, luigi scarso wrote: > On Tue, Oct 24, 2017 at 9:15 AM, Hans Hagen wrote: >> >> Well, for me it means that all that validation esp of keys like this are >> rather useless (creating work) because docs validated in the past and >> archived now are suddenly no longer valid. >

Re: [dev-context] fix output intent subtype

On 10/24/2017 07:51 PM, luigi scarso wrote: > On Tue, Oct 24, 2017 at 7:42 PM, Pablo Rodriguez wrote: >> >> But replacing vectors with bitmaps is a way of avoiding the issue, not >> of fixing it (if this needs to be fixed). > > yes, it's a clean way to resolve a problem that could not be

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 7:42 PM, Pablo Rodriguez wrote: > On 10/24/2017 07:06 PM, luigi scarso wrote: >> a pdf ? >> As said previously , including pdf can break the rules of >> format=PDF/A-3a. >> Simply include bitmap images, it's way more robust. > > Allow me a fair and respectful

Re: [dev-context] fix output intent subtype

On 10/24/2017 07:06 PM, luigi scarso wrote: > a pdf ? > As said previously , including pdf can break the rules of > format=PDF/A-3a. > Simply include bitmap images, it's way more robust. Allow me a fair and respectful disagreement, Luigi. Bitmap images are less problematic in PDF/A because they

Re: [dev-context] fix output intent subtype

On Tue, 24 Oct 2017 19:06:51 +0200 luigi scarso wrote: > is this > \externalfigure[cow] > a pdf ? > As said previously , including pdf can break the rules of > format=PDF/A-3a. > Simply include bitmap images, it's way more robust. Isn't that non-optimal, using

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 7:02 PM, Pablo Rodriguez wrote: > On 10/24/2017 01:48 PM, Peter Rolf wrote: >> [...] >> Well, the good news is that the actual problem does not effect any A1 >> documents. And even with an incomplete (99.9%) validity the documents >> stay usable. I'm sure

Re: [dev-context] fix output intent subtype

On Tue, 24 Oct 2017 19:46:21 +0200 luigi scarso wrote: > On Tue, Oct 24, 2017 at 7:27 PM, Alan Braslau > wrote: > > On Tue, 24 Oct 2017 19:06:51 +0200 > > luigi scarso wrote: > > > >> is this > >>

Re: [dev-context] fix output intent subtype

On 10/24/2017 01:48 PM, Peter Rolf wrote: > [...] > Well, the good news is that the actual problem does not effect any A1 > documents. And even with an incomplete (99.9%) validity the documents > stay usable. I'm sure that (alien) historians will love any ConTeXt > created PDF/A document :D

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 7:27 PM, Alan Braslau wrote: > On Tue, 24 Oct 2017 19:06:51 +0200 > luigi scarso wrote: > >> is this >> \externalfigure[cow] >> a pdf ? >> As said previously , including pdf can break the rules of >> format=PDF/A-3a.

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 8:21 PM, Alan Braslau wrote: > "Let the buyer beware". > > Given that bitmap graphics are NOT OK (think bloat, an MS/Office > specialty), there must be a better solution. Perhaps simply detecting a > conflict between an included PDF and the "host"

Re: [dev-context] fix output intent subtype

On 10/24/2017 09:38 PM, Hans Hagen wrote: > On 10/24/2017 8:21 PM, Pablo Rodriguez wrote: >> It adds them a color space that (I think) makes it impossible that an >> icc profile can be referred to the form xobject. > > Are you sure? The image is included as is. Nothing is added to its > resource

Re: [dev-context] fix output intent subtype

On 10/24/2017 8:21 PM, Alan Braslau wrote: On Tue, 24 Oct 2017 19:46:21 +0200 luigi scarso wrote: On Tue, Oct 24, 2017 at 7:27 PM, Alan Braslau wrote: On Tue, 24 Oct 2017 19:06:51 +0200 luigi scarso wrote: is

Re: [dev-context] fix output intent subtype

Am 24.10.2017 um 19:51 schrieb luigi scarso: > On Tue, Oct 24, 2017 at 7:42 PM, Pablo Rodriguez wrote: >> On 10/24/2017 07:06 PM, luigi scarso wrote: >>> a pdf ? >>> As said previously , including pdf can break the rules of >>> format=PDF/A-3a. >>> Simply include bitmap images, it's

Re: [dev-context] fix output intent subtype

On Tue, Oct 24, 2017 at 9:48 PM, Pablo Rodriguez wrote: > I will investigate the issue myself and report here (or in the user > list) the results. this is the right list -- luigi ___ dev-context mailing list dev-context@ntg.nl