-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table 401: Solidities and CxF spectral data are mutually exclusive #466
Comments
If we were to consider this change, then we first need to change PDF/X-6 to ensure that all existing PDF/X-6 files will remain valid according to the current restricted definition in ISO 32000-2:2020 - and only then PDF 2.0 could be relaxed... |
PDF/X-6 does not say anything about consistency between CxF and Solidities, therefore there is no change required in PDF/X-6. |
PDF/X-6 doesn't need to explicitly mention anything since it automatically "inherits" all "shall" requirements from ISO 32000-2:2020. My concern is that we do not want to invalidate any existing PDF/X-6 files, nor do we want to have a situation where PDF/X-6 processors processing PDF/X-6 files with different CxF rules could result in appearance differences (as the primary goal of PDF/X-6 is to avoid visual differences). Hence we need to avoid PDF/X-6 to including this technical change - that would need to be a new standard. |
IMO we cannot just allow both entries without specifying under what circumstances which wins over the other. It is also not straightforward for a preflight application to check consistency between the two. But even if that would be the case you would have to have a corresponding "shall" statement in either PDF/X-6 or PDF 2.0 and I think we all agree that the first would be better. So, in any case I agree with Peter that we would first have to adjust PDF/X. |
@bertvankerckhove you are right that the limitation should at some point be relaxed, but I think it should at the same time be explicit about what wins when. |
This is what PDF/X-6 says about CxF. 6.19 Spectral Data (CxF) The spirit of this clause that usage of CxF is entirely optional but that CxF data should be consistent with other PDF data used in rendering. The “may” in the first sentence says that a conforming processor is free to use or ignore the CxF data under all conditions. The 2nd sentence says that a writer should ensure that CxF spectral data is consistent with the output intent ICC profile. So the path forward that seems to make most sense is
To answer Dietrich's other question: there is customer demand to have PDFs with both Solidities+PrintingOrder and CxF. |
The PDF TWG will discuss this issue on 7 Nov here in Prague (please join us if you can!) so we can further discuss during the 2 Dec ISO TC 130 WG 2 meeting w.r.t. the current in-process PDF/X-6 dated revision. |
At the time that we added support for CxF to PDF, CxF was still new and not fully proven in the industry - let alone with PDF - and so we took the safest route based on what we knew at the time. And it's gotten us far enough to learn that we need to make changes. So be it. However, to support @DietrichSeggern - we cannot make ANY changes in the current text UNLESS we have something that fully describes "who wins" and "how to determine inconsistency" in all cases. If the printing industry (e.g. @bertvankerckhove @Lieven-Plettinck ), who understands customer & technical requirements, can provide some specific wording for those scenarios, then I am sure we can work out a workable solution for all. |
PDF TWG agree that PDF/X-6 must NOT support this change. To be discussed in TC 130 WG 2. |
Consistency The CxF data for a certain PDF colorant contain a series of spectral reflectance measurements of patches. There are one or more patches of a tint of the colorant printed over the clear substrate. There are optionally one or more patches of a tint of the colorant over black. 1-Taking the spectral measurement of 100% of the tint of the colorant over clear substrate allows to calculate absolute colorimetric coordinates for the 100% tint of the colorant printed on the substrate. Combining this with the substrate absolute color coordinates that can be calculated from the spectral measurement of the patch of 0% of the colorant on substrate, allows to calculate relative colorimetric coordinates of the 100% tint of the colorant on clear substrate. Above results should be consistent with the alternate color space representation of the colorant in the PDF in the Separation or DeviceN colorspace i.e. leading to the same device independent color coordinates. 2-Taking the spectral measurements of the tints of the colorant printed on clear substrate and on black allows to calculate the transparency (or the reverse the solidity) of a colorant in function of wavelength. From this an average, wavelength independent, transparency or solidity can be calculated. This result should be consistent with the value in the Solidities dictionary. I hope above text already helps to understand better what consistency means. Who wins I still don't understand why it is needed to specify which data set wins. If it would be stated that CxF (being the richer data set) wins over Solidites and alternate colorspace, we would make CxF support mandatory for every PDF/X-6 processor. If it would be stated that Solidities and alternate colorspace wins over CxF, any PDF/X-6 processor would be prevented from using CxF. But maybe a way out of this contradiction is to state:
|
ISO 32000-2:2020 Table 401 says:
In the text for MixingHints
In the text for SpectralData
In other words a PDF colorant can have a solidity (inverse of transparency) or there can be spectral data but not both.
The argument for this mutual exclusivity is mentioned in the notes. The spectral data can in some cases be used to calculate transparency of a colorant used in printing in function of wavelength.
This results of this calculation could be inconsistent with the colorant transparency/solidity as indicated in the MixingHints/Solidities.
To exclude this potential inconsistency ISO 32000-2 forbids to have both solidity and spectral data for a PDF colorant.
This limits important use cases:
• Spectral data can in some cases be used to calculate transparency of a colorant (e.g. when there are spectral reflectance measurement data for patches over clear substrate and over black) but not always (e.g when there are only measurement data for patches on clear substrate). In such a case the solidity/transparency for the colorant in the Solidities can be used as an approximate transparency averaged over wavelength.
• PDF files can be used in multiple applications, some of these applications may be CxF capable, other applications may not be CxF capable.
Having both solidities and CxF data for a colorant in the PDF would allow CxF capable applications to use to render the PDF with the highest accuracy while non CxF capable applications can render a reasonable approximation.
This limitation on Solidities versus CxF does not eliminate the risk of inconsistency of CxF data with other data in the PDF. As a matter of fact an even larger inconsistency is possible between the CxF data and the alternate color space representation of a spot color. Here the spectral reflectance measurement data in the CxF of the 100% patch of a colorant would need to be consistent with the Lab data of the colorant in the alternate colorspace.
Since the mutual exclusion clauses for Solidities and SpectralData blocks important use cases while not being effective to exclude inconsistency, we suggest to relax the limitation by indicating there should be consistency between SpectralData, Solidities and alternate color space representation of PDF colorants while not excluding presence of such data.
(Checking consistency is something that preflight applications can take care of.)
The text was updated successfully, but these errors were encountered: