On Tue, Oct 24, 2017 at 10:01 AM, Peter Rolf <peter.r...@arcor.de> 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
> donno them).
>
> Anyhow, I'll download veraPDF and test all variants with the actual
> beta. I doubt that the results will differ. If I find any other errors
> you can fix them at one go. Will report back (probably after lunch
> break). I hope nobody is in a hurry :D
I have made a test with pdf/a-2a, pdf/a-3a, they pass both the
verapdf 1.8.4 and 1.9.46-dev
The problem with the file
$ cat unrgb.tex
\nopdfcompression
\setupexternalfigures[location=default]
\setuptagging[state=start]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB.icc,default_gray.icc},
level=0]
\setupcolors[cmyk=no, pagecolormodel=auto]
\starttext
\startTEXpage[offset=1em]
\externalfigure[cow-brown]
\stopTEXpage
\stoptext
is that it includes a pdf (cow-brown.pdf) and this can lead to
conflicts with the specs. of the setupbackend.
There is no way to solve this: even is both the pdf are pdf/a-3a ok,
they can conflict.
So, the safest way is always to include bitmap images.
--
luigi
_______________________________________________
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context
