ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Jan Heinen <JaHeinen@gmx.de>
Subject: Re: Preparing the print: ICC-Profiles, Fogra, (in german untranslatable)
Date: Fri, 24 Feb 2012 17:20:53 +0100	[thread overview]
Message-ID: <4F47B8E5.7010100@gmx.net> (raw)
In-Reply-To: <4F4779C3.8060600@gmx.de>

Am 24.02.2012 12:51, schrieb Jan Heinen:
> My book is ready and I want to print it next week.
> 
> 1. The printer told me to set up my PDF with the following values:
> PDF/X-1a:2003,
> ISO Coated v2 (ECI)
> 
> 2. And I did:
> 
> \setupbackend
>  [format=PDF/X-1a:2003,
>   intent={ISO Coated v2 (ECI)}]
> 
> 3. Then I send a test-PDF to my printer and got the following answer:
> 
> 4. The printers answer in german:
> Die Ausgabebedingung ist mit FOGRA 39 hinterlegt. Dadurch erscheint eine
> falsche Farbvoransicht. FOGRA 39 sind "nur" Charakterisierungsdaten zur
> Erzeugung von ICC-Profilen für die entsprechenden Ausgabebedingungen.
> Wenn die Bilddaten in den "ISO Coated v2 (ECI)"  Farbraum separiert
> wurden, sollte dieser am Besten hier als Name hinterlegt werden. Die
> Kennung der Ausgabebedingung wäre "Fogra 39".
> 
> I failed trying to translate this answer into english. I hope there is
> someone here who understands the german answer.
> 

4. The printers answer in (d)english:
The output condition is set to 'FOGRA39', which results in wrong colors
in the output preview.
'FOGRA39' is 'only' the label for the characterization data, which are
used for the creation of icc profiles with according output conditions.
For the image data separation to the 'ISO Coated v2 (ECI)' color space
it's best to use the identifier 'Fogra 39'.


The related 'id' field is used to set the so called
'OutputConditionIdentifier' entry in the output intent. In the
definition of 'OutputConditionIdentifier' (PDF Reference, version 1.7,
p.971) it says:

    ...

    A typical value for this entry would be the name of a production
    condition maintained in an industry-standard registry such as
    the ICC Characterisation Data Registry (see the Bibliography). If
    the designated condition matches that in effect at production
    time, the production software is responsible for providing the
    corresponding ICC profile as defined in the registry.

    ...

Here is a list of the registered CMYK characterization data sets for
standard printing processes.

    http://www.color.org/chardata/drsection1.xalter

**Only capital letters, no spaces in the fogra entries.**
Mh, have I missed something here?


My assumption: the separation software makes the wrong decision based on
the 'OutputConditionIdentifier' entry.
A reason for this could be, that the icc profile for the output intent
is **NOT EMBEDDED**, so the software is forced to search its own icc
profile library (which fails).

Possible solution A:

embed the profile (\setupbackend[..., option=always] ) and hope
that the software uses the included profile (should be the standard)

Possible solution B:

change the 'id' entry to a proprietary standard and hope that the
software uses the right profile


Just out of curiosity: which separator software does the printing house use?


Best wishes,  Peter

___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2012-02-24 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 11:51 Jan Heinen
2012-02-24 12:00 ` luigi scarso
2012-02-24 12:18 ` Henning Hraban Ramm
2012-02-24 13:05 ` Peter Rolf
2012-02-24 16:20 ` Peter Rolf [this message]
2012-02-24 16:25   ` luigi scarso

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=4F47B8E5.7010100@gmx.net \
    --to=indiego@gmx.net \
    --cc=JaHeinen@gmx.de \
    --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).