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 08:58:19 +0100 [thread overview]
Message-ID: <8D0C91B8-EDFC-4BD4-B479-F54CC0997C7A@fiee.net> (raw)
In-Reply-To: <d33d23cf-e4ff-516e-02c5-3be9676b72b1@klankschap.nl>
> Am 01.11.2021 um 08:05 schrieb Floris van Manen via ntg-context <ntg-context@ntg.nl>:
>
> this document:
>> and also extendedhttps://wiki.contextgarden.net/PDFX a bit.
>
> contains a link to the Ghent Workshop that returns a 404
>
> [here] -> http://www.gwg.org/recommended_ICC_profiles.phtm -> 404
Thank you. The information from 2008 was outdated anyway; GWG’s latest recommendations from 2015 don’t contain ICC profiles any more (maybe their settings for commercial applications do, didn’t check).
And it seems like GWG is in conflict with the PDF association, at least GWG’s recommendations contradict PDF/X.
I’ll try to reflect both...
From my personal experience:
– If you don’t exactly know what you’re doing, you should use sRGB as RGB working color space, because most cameras and scanners use it. Yes, parts of the color space are outside the printable range, that’s why GWG (used to) recommend ECI RGB.
– Don’t use CMYK images, since they’re bigger, and if they’re not in the same CMYK color space as the one used by the printshop, the conversion is more lossy than any RGB-CMYK conversion.
– You can use DeviceCMYK (i.e. without profile) for graphical elements, that’s what GWG recommends, but it’s against PDF/X-3+.
– Use the latest FOGRA (Coated/Uncoated) CMYK profile as output intent, at least that’s what German/European printshops use in offset and digital printing. If not, your printshop should tell you which profile they use.
– For printing in the USA, use a SWOP CMYK profile as output intent. (SWOP and Euroscale CMYK colors are visibly different!)
– I don’t know about printshops in other parts of the world.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-11-01 7:58 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 ` Henning Hraban Ramm via ntg-context [this message]
2021-11-01 8:07 ` Color profiles (was: Bloody PDF boxes) Henning Hraban Ramm via ntg-context
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=8D0C91B8-EDFC-4BD4-B479-F54CC0997C7A@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).