Hi all, again I have a question concerning color profiles. I have this to load the ISO Coated v2 300% profile. \setupbackend[ format=PDF/X-3:2003, intent={ISO Coated v2 300\letterpercent\space (ECI)}, ] \setupcolors[cmyk=yes,rgb=no,] But is this profile part of the new lmtx version? I get this in my logs backend > profiles > profile specification 'ISO Coated v2 300% (ECI)' loaded from '/home/juh/context-linux-64/tex/texmf-context/colors/icc/context/colorprofiles.xml' But I am not sure whether the profile is really loaded. In the old context distribution I had to put the profile in texmf-local. There is this in lmtx: ~/context-linux-64/tex/texmf-context/colors/icc/profiles$ ls -l insgesamt 3652 -rw-r--r-- 1 juh juh 416 Jan 6 16:32 default_gray.icc -rw-r--r-- 1 juh juh 1992 Jan 6 16:32 ecirgb_v2.icc -rw-r--r-- 1 juh juh 700 Jan 6 16:32 ecirgb_v2_iccv4.icc -rw-r--r-- 1 juh juh 1829093 Jan 6 16:32 isocoated_v2_300_eci.icc -rw-r--r-- 1 juh juh 1829077 Jan 6 16:32 isocoated_v2_eci.icc -rw-r--r-- 1 juh juh 3144 Jan 6 16:32 srgb.icc -rw-r--r-- 1 juh juh 60960 Jan 6 16:32 srgb_v4_icc_preference.icc I am not sure if the file name matches as in profiles.xml we have this with mixed upper and lower cases: <profile> <filename>ISOcoated_v2_300_eci.icc</filename> <colorspace>CMYK</colorspace> <class>prtr</class> <id>FOGRA39</id> <info>ISO Coated v2 300% (ECI)</info> <checksum>e14f5db955711d914d877df35ad7a1b5</checksum> <version>24000000</version> <url>http://www.color.org</url> <outputcondition>Offset printing, according to ISO 12647-2:2004/Amd 1, OFCOM, paper type 1 or 2 = coated art, 115 g/m2, tone value increase curves A (CMY) and B (K)</outputcondition> </profile> Is there a linux tool to test if the correct profile is part of the pdf? Any hints? TIA juh -- Autoren-Homepage: ......... http://literatur.hasecke.com Satiren & Essays: ......... http://www.sudelbuch.de Privater Blog: ............ http://www.hasecke.eu Netzliteratur-Projekt: .... http://www.generationenprojekt.de
Am 12.02.2020 um 09:41 schrieb juh:
Hi all,
again I have a question concerning color profiles.
I have this to load the ISO Coated v2 300% profile.
\setupbackend[ format=PDF/X-3:2003, intent={ISO Coated v2 300\letterpercent\space (ECI)}, ]
\setupcolors[cmyk=yes,rgb=no,]
But is this profile part of the new lmtx version?
I get this in my logs
backend > profiles > profile specification 'ISO Coated v2 300% (ECI)' loaded from '/home/juh/context-linux-64/tex/texmf-context/colors/icc/context/colorprofiles.xml'
But I am not sure whether the profile is really loaded.
In the old context distribution I had to put the profile in texmf-local.
There is this in lmtx:
~/context-linux-64/tex/texmf-context/colors/icc/profiles$ ls -l insgesamt 3652 -rw-r--r-- 1 juh juh 416 Jan 6 16:32 default_gray.icc -rw-r--r-- 1 juh juh 1992 Jan 6 16:32 ecirgb_v2.icc -rw-r--r-- 1 juh juh 700 Jan 6 16:32 ecirgb_v2_iccv4.icc -rw-r--r-- 1 juh juh 1829093 Jan 6 16:32 isocoated_v2_300_eci.icc -rw-r--r-- 1 juh juh 1829077 Jan 6 16:32 isocoated_v2_eci.icc -rw-r--r-- 1 juh juh 3144 Jan 6 16:32 srgb.icc -rw-r--r-- 1 juh juh 60960 Jan 6 16:32 srgb_v4_icc_preference.icc
I am not sure if the file name matches as in profiles.xml we have this with mixed upper and lower cases:
<profile> <filename>ISOcoated_v2_300_eci.icc</filename> <colorspace>CMYK</colorspace> <class>prtr</class> <id>FOGRA39</id> <info>ISO Coated v2 300% (ECI)</info> <checksum>e14f5db955711d914d877df35ad7a1b5</checksum> <version>24000000</version> <url>http://www.color.org</url> <outputcondition>Offset printing, according to ISO 12647-2:2004/Amd 1, OFCOM, paper type 1 or 2 = coated art, 115 g/m2, tone value increase curves A (CMY) and B (K)</outputcondition> </profile>
Is there a linux tool to test if the correct profile is part of the pdf?
Any hints? TIA juh
Hi juh, I guess the problem are the file names of the profiles. On Windows it doesn't matter if you use upper or lower case letters. AFAIK Linux handles that differently. In the end the <filename> entries in "[..]/texmf-context/colors/icc/context/colorprofiles.xml" and the real file names must be "equal" for all OS. Add \enabletrackers[backend.pdfx] to your document to get more info about the profile inclusion. Not sure if this is the correct tracker though... no time to check, as I have to make lunch now. Hope that helps, Peter
Am 12.02.20 um 11:09 schrieb Peter Rolf:
I get this in my logs
backend > profiles > profile specification 'ISO Coated v2 300% (ECI)' loaded from '/home/juh/context-linux-64/tex/texmf-context/colors/icc/context/colorprofiles.xml'
I just realized that the above output is the right output. Ok. But now I have another question I want to install a new profile I downloaded from eci.org I extended colorprofiles.xml putting it in texmf-local/colors/icc/context/ with this additional xml: <profile> <filename>PSO_Uncoated_ISO12647_eci.icc</filename> <colorspace>CMYK</colorspace> <class>prtr</class> <id>Custom</id> <info>PSO Uncoated ISO12647 ECI</info> <checksum>ae81087e1c54c6fdda2f93bd2d47cfaf</checksum> <version>2000000</version> <url>http://www.eci.org</url> <outputcondition>Commercial and specialty offset, paper type 4, uncoated white paper, positive plates, tone value increase curves C (CMY) and D (K), white backing. </outputcondition> </profile> I generated the md5 checksum from the file PSO_Uncoated_ISO12647_eci.icc. But the file in texmf-local is not found backend > profiles > profile specification 'PSO Uncoated ISO12647 ECI' not found in 'colorprofiles.xml, colorprofiles.lua' How can I make context aware of the files? TIA juh
On 2/12/20 5:15 PM, Jan U. Hasecke wrote:
[...] I just realized that the above output is the right output.
Hi Jan Ulrich, you might check profiles that with VeraPDF (or simply \nopdfcompression as first command in the source and search for the profile 😎),
Ok. But now I have another question
I want to install a new profile I downloaded from eci.org [...] But the file in texmf-local is not found
backend > profiles > profile specification 'PSO Uncoated ISO12647 ECI' not found in 'colorprofiles.xml, colorprofiles.lua'
How can I make context aware of the files?
How about deleting the cache (simply remove tex/context-cache/luatex-cache) and generate it again (by running "mtxrun --generate", before compiling your source again? I hope it helps, Pablo -- http://www.ousia.tk
Am 12.02.20 um 19:48 schrieb Pablo Rodriguez:
On 2/12/20 5:15 PM, Jan U. Hasecke wrote:
[...] I just realized that the above output is the right output.
Hi Jan Ulrich,
you might check profiles that with VeraPDF (or simply \nopdfcompression as first command in the source and search for the profile 😎),
Ok. But now I have another question
I want to install a new profile I downloaded from eci.org [...] But the file in texmf-local is not found
backend > profiles > profile specification 'PSO Uncoated ISO12647 ECI' not found in 'colorprofiles.xml, colorprofiles.lua'
How can I make context aware of the files?
How about deleting the cache (simply remove tex/context-cache/luatex-cache) and generate it again (by running "mtxrun --generate", before compiling your source again?
I get the error that was reported in another thread. :-( resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) .sh ./install.sh was the solution. I cannot use mtxrun in a way like "mtxrun --locate" in lmtx: $ mtxrun --locate mtxrun | forcing cache reload resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/juh/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/juh/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/juh/texmf-context/web2c' from specification 'selfautoparent:/texmf-context/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/juh/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/juh/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/juh/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/juh/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/juh/texmf-context/web2c' from specification 'selfautoparent:/texmf-context/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/juh/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/juh/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | the resolver databases are not present or outdated
Am 12.02.2020 um 17:15 schrieb Jan U. Hasecke:
Am 12.02.20 um 11:09 schrieb Peter Rolf:
I get this in my logs
backend > profiles > profile specification 'ISO Coated v2 300% (ECI)' loaded from '/home/juh/context-linux-64/tex/texmf-context/colors/icc/context/colorprofiles.xml'
I just realized that the above output is the right output.
Ok. But now I have another question
I want to install a new profile I downloaded from eci.org
I extended colorprofiles.xml putting it in texmf-local/colors/icc/context/ with this additional xml:
<profile> <filename>PSO_Uncoated_ISO12647_eci.icc</filename> <colorspace>CMYK</colorspace> <class>prtr</class> <id>Custom</id> <info>PSO Uncoated ISO12647 ECI</info> <checksum>ae81087e1c54c6fdda2f93bd2d47cfaf</checksum> <version>2000000</version> <url>http://www.eci.org</url> <outputcondition>Commercial and specialty offset, paper type 4, uncoated white paper, positive plates, tone value increase curves C (CMY) and D (K), white backing. </outputcondition> </profile>
I generated the md5 checksum from the file PSO_Uncoated_ISO12647_eci.icc.
But the file in texmf-local is not found
backend > profiles > profile specification 'PSO Uncoated ISO12647 ECI' not found in 'colorprofiles.xml, colorprofiles.lua'
How can I make context aware of the files?
Just tried to do the same and after some fiddling it worked. I used this settings for the profile (slightly modified) <profile> <filename>PSO_Uncoated_ISO12647_eci.icc</filename> <colorspace>CMYK</colorspace> <class>prtr</class> <id>Fogra47L</id> <info>PSO Uncoated ISO12647 (ECI)</info> <checksum>ae81087e1c54c6fdda2f93bd2d47cfaf</checksum> <version>2000000</version> <url>http://www.eci.org</url> <outputcondition>Commercial and specialty offset, paper type 4, uncoated white paper, positive plates, tone value increase curves C (CMY) and D (K), white backing. </outputcondition> </profile> Copy the icc-profile into the same folder as the shipped profiles. Call "context --make" to make a new format, update the file database. %---------------------- \enabletrackers[backend.pdfx] \setupbackend[ format=PDF/X-3:2003, intent={PSO Uncoated ISO12647 (ECI)}, ] \setupcolors[cmyk=yes,rgb=no] \nopdfcompression \starttext foo \stoptext %----------------------- The produced PDF has a size of 1.7MB. Tested with context --version mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: r:/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.01.26 18:34 mtx-context | main context file: r:/tex/texmf-context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.01.26 18:34
participants (4)
-
Jan U. Hasecke -
juh
-
Pablo Rodriguez -
Peter Rolf