From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: ICC profiles for \externalfigure
Date: Tue, 10 Oct 2017 22:09:06 +0200 [thread overview]
Message-ID: <23a89473-3c49-8666-9817-c2261ae6c287@gmx.es> (raw)
In-Reply-To: <285b5572-2a24-8d86-9913-285537758629@wxs.nl>
On 10/10/2017 01:02 AM, Hans Hagen wrote:
> as said, it will not be an engine supported features as it's technically
> impossible without messing up the backend (and we don't want to mess up
> stable code with fragile hacks)
Many thanks for the reply, Hans.
I understand the problem now with fragile hacks. Sorry for having
insisted in my proposal.
I fixed the external PDF figure (http://pdf.ousia.tk/icc-vector.pdf) and
I used with in the following sample:
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
profile={sRGB.icc,default_gray.icc},
level=0]
\setuptagging[state=start]
\setupcolors[cmyk=no, pagecolormodel=auto]
\startTEXpage[offset=1em]
\externalfigure[icc-vector.pdf]
\stopTEXpage
\stoptext
http://pdf.ousia.tk/icc-vector.pdf is the same graphic as
http://pdf.ousia.tk/basic-figures.pdf, but with an ICC profile. The
veraPDF validator (http://verapdf.org) says it’s a valid PDF/A-1b document.
But the output from the sample above
(http://pdf.ousia.tk/xobject-noicc.pdf) isn’t a valid PDF/A document.
The external figure has no ICC profile.
The uncompressed PDF document reveals that the XObject has no reference
to any ICC profile.
I’m afraid this might be a bug.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2017-10-10 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 9:09 Pablo Rodriguez
2017-10-09 18:16 ` Hans Hagen
2017-10-09 19:55 ` Pablo Rodriguez
2017-10-09 23:02 ` Hans Hagen
2017-10-10 9:27 ` Henning Hraban Ramm
2017-10-10 20:11 ` Pablo Rodriguez
2017-10-10 20:09 ` Pablo Rodriguez [this message]
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=23a89473-3c49-8666-9817-c2261ae6c287@gmx.es \
--to=oinos@gmx.es \
--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).