From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Color profiles (was: Bloody PDF boxes)
Date: Mon, 1 Nov 2021 09:07:48 +0100 [thread overview]
Message-ID: <3A296E6D-6E5F-4694-BF56-5837A069B3A8@fiee.net> (raw)
In-Reply-To: <8D0C91B8-EDFC-4BD4-B479-F54CC0997C7A@fiee.net>
> Am 01.11.2021 um 08:58 schrieb Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>:
>
> And it seems like GWG is in conflict with the PDF association, at least GWG’s recommendations contradict PDF/X.
GWG doesn’t want to contradict but has a quality focus, see https://www.pdfa.org/further-quality-requirements-pdfx-plus/
(I attended a few workshops by the author Stephan Jaeggi in about 2005...)
Hraban
___________________________________________________________________________________
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:[~2021-11-01 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 10:36 Bloody PDF boxes and cr*p marks! Henning Hraban Ramm via ntg-context
2021-10-12 11:15 ` Hans Hagen via ntg-context
2021-10-12 16:18 ` Henning Hraban Ramm via ntg-context
2021-10-12 18:48 ` Hans Hagen via ntg-context
2021-10-19 20:10 ` Henning Hraban Ramm via ntg-context
2021-10-30 19:21 ` Henning Hraban Ramm via ntg-context
2021-11-01 5:45 ` Duncan Hothersall via ntg-context
2021-11-01 7:05 ` Floris van Manen via ntg-context
2021-11-01 7:58 ` Color profiles (was: Bloody PDF boxes) Henning Hraban Ramm via ntg-context
2021-11-01 8:07 ` Henning Hraban Ramm via ntg-context [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=3A296E6D-6E5F-4694-BF56-5837A069B3A8@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).