I know I have raised this before, but I continue to be confused. I spoke with our printer dept and they told me I need to use Coated FOGRA39 (ISO 12647-2:2004) as intent. 1. I checked the wiki and it tells me that Predefined output intents includes the above intent. But my log file tells me: backend > profiles > profile specification 'Coated FOGRA39' not found in 'colorprofiles.xml, colorprofiles.lua'. (I am using ConTeXt ver: 2022.08.25) 2. I checked on the internet re colorprofile files and it tells me that I can download Coated_Fogra39L_VIGC_300.icc as an icc version that is commonly used by Adobe and I feel sure it would be sufficient for my printer's purposes. I placed it where the other profile files are located in the ConTeXt tree /context/tex/texmf-context/colors/icc/profiles 3. It is still not recognised, but perhaps I have to run a command for that to happen. My question(s): - is my procedure correct? In other words, can I place such a file in the profiles subfolder and expect it to work? - do I need to run a particular context -- command for this to happen? Julian
On 6/15/25 03:30, jbf wrote:
I know I have raised this before, but I continue to be confused. I spoke with our printer dept and they told me I need to use Coated FOGRA39 (ISO 12647-2:2004) as intent.
Hi Julian, according to `colorprofiles.xml` (from the oldest standalone I have, from 2023.01.04 11:35), this should include your intent: \setupbackend[ format=PDF/X-1a:2001, intent={Coated FOGRA39 (ISO 12647-2:2004)}, %intent={ISO Coated v2 300\letterpercent\space (ECI)}, ] \starttext \null \stoptext BTW, the added intent is also FOGRA39 (see description in `colorprofiles.xml`).
1. I checked the wiki and it tells me that Predefined output intents includes the above intent.
Is https://wiki.contextgarden.net/Input_and_compilation/PDF/PDFX the link?
But my log file tells me:
backend > profiles > profile specification 'Coated FOGRA39' not found in 'colorprofiles.xml, colorprofiles.lua'. (I am using ConTeXt ver: 2022.08.25)
Check the sample above and always include a minimal sample that shows your problem (otherwise even samples provided to you may not show the issue you are facing). But I guess (from what I read in your error message) is that you may need to replace `intent={Coated FOGRA39}` with `intent={Coated FOGRA39 (ISO 12647-2:2004)}`. Just as a comment, almost three years ago feels like ancient in ConTeXt releases. (I mean, without checking, I cannot tell for sure that LMTX was available back then [sorry, I won’t check that].)
2. I checked on the internet re colorprofile files and it tells me that I can download Coated_Fogra39L_VIGC_300.icc as an icc version that is commonly used by Adobe and I feel sure it would be sufficient for my printer's purposes. I placed it where the other profile files are located in the ConTeXt tree /context/tex/texmf-context/colors/icc/profiles
This works (I have to do it myself), as long as: 1. You may place the .icc file in %USERPROFILE%/texmf/texmf-local/ (using Windwos or $HOME/texmf/texmf-local/ in Unix [Linux or macOS]). 2. You need to rename it (or make a symlink, as you prefer) to `CoatedFOGRA39.icc`, since this is the name contained in `colorprofiles.xml`. 3. You need to set you `intent` value to `Coated FOGRA39 (ISO 12647-2:2004)` (as `colorprofiles.xml` expects). 4. It worked for me (using $HOME/texmf/), but new files in the main tree may require erasing the cache and regenerating it again (`mtxrun --script cache --erase && mtxrun --generate`). Of course, if this doesn’t work for you, please provide a minimal sample and the error message.
3. It is still not recognised, but perhaps I have to run a command for that to happen.
No, you need to set the right values for the `\setupbackend` command (as for any other ConTeXt command).
My question(s):
- is my procedure correct? In other words, can I place such a file in the profiles subfolder and expect it to work?
If you allow me, maybe you chain of thought needs some adjustments (in the details, where many bugs and issues live), but your expectations might have been set too high. If a file name is used to embed a file, they have to be exactly the same (in Unix, even with case distinction [macOS may be fuzzy here]). The same applies for intent names. (Yesterday, we found out that a profile wasn’t being loaded because of a missing comma after the closing parenthesis [“it’s in the details”].) It isn’t a mantra, please provide a minimal sample which displays the issue you are facing. Again, this increases the probability of getting a reply. You may also have the issue with your own code or it may be that only that code hits a bug in ConTeXt. I hope it helps, Pablo
Pablo, let me respond to each of the items below: 1. The logfile result, using your example below produces: backend > profiles > profile specification 'Coated FOGRA39 (ISO 12647-2:2004)' loaded from '/home/julian/bin/context/tex/texmf-context/colors/icc/context/colorprofiles.xml' backend > profiles > omitting reference to profile for intent 'Coated FOGRA39 (ISO 12647-2:2004)' So I assume that my difficulty initially was to omit the curly brackets, or that I placed an abbreviated statement, just Coated FOGRA39. I do not know why the log then tells me 'omitting reference to...', but perhaps this is not a problem. Or maybe the problem was that I thought I did not also need to include (ISO 1267-2:2004). I thought that was simply a descriptor and not necessary. So perhaps I needed to complete the whole statement, namely {Coated FOGRA39 (ISO 12647-2:2004)}. 2. Are you also saying that {ISO Coated v2 etc.} is exactly the same? 3. Yes https://wiki.contextgarden.net/Input_and_compilation/PDF/PDFX is the link. 4. Be assured that the 2022 version is LMTX and that it has worked without difficulty for me. I also have a most recent version sitting on the computer, but until I am sure that I have resolved this 'intent' issue, I do not want to switch. To be honest, I have looked in the 'profiles' folder of the latest version and I did not see the Coated FOGRA39 file. Hence my hesitation. The folder contains eight *.icc profile files, none of them FOGRA. (but see further on in 5. below) 5. I will have to read your comments more carefully about my downloaded file (if indeed I now still need it, perhaps not) so I can understand what you have said. I am a Linux user. My basic problem may well be a very poor understanding of this whole colorprofile issue and how it works. For example, I have told you that I see just 8 color profile files in the 'profile' folder, but of course I did not look at the colorprofile.xml file (in the color folder), and now that I look at the colorprofile.xml file, I see my FOGRA39 profile mentioned between lines 207-2015. Indeed, looking at the colorprofile.lua, I see that it is precisely this intent that is there as an example. Yes, I understand what you are saying about minimal examples, so sorry that I did not give you the exact intent line in my code. I have now set them up as you have indicated in your example, with the log file result that I have shown you in no. 1 above. It would seem to have resolved my problem, other than the fact that I don't understand the implications when its says 'omitting reference to profile for intent...'. Does that mean that the whole things wasn't really all that important in the first place?? You are a very patient person, Pablo, and I am grateful for that! I will send the PDF file from this to the printers and assume that all is well! Julian On 15/6/25 17:48, Pablo Rodriguez via ntg-context wrote:
On 6/15/25 03:30, jbf wrote:
I know I have raised this before, but I continue to be confused. I spoke with our printer dept and they told me I need to use Coated FOGRA39 (ISO 12647-2:2004) as intent. Hi Julian,
according to `colorprofiles.xml` (from the oldest standalone I have, from 2023.01.04 11:35), this should include your intent:
\setupbackend[ format=PDF/X-1a:2001, intent={Coated FOGRA39 (ISO 12647-2:2004)}, %intent={ISO Coated v2 300\letterpercent\space (ECI)}, ] \starttext \null \stoptext
BTW, the added intent is also FOGRA39 (see description in `colorprofiles.xml`).
1. I checked the wiki and it tells me that Predefined output intents includes the above intent. Is https://wiki.contextgarden.net/Input_and_compilation/PDF/PDFX the link?
But my log file tells me:
backend > profiles > profile specification 'Coated FOGRA39' not found in 'colorprofiles.xml, colorprofiles.lua'. (I am using ConTeXt ver: 2022.08.25) Check the sample above and always include a minimal sample that shows your problem (otherwise even samples provided to you may not show the issue you are facing).
But I guess (from what I read in your error message) is that you may need to replace `intent={Coated FOGRA39}` with `intent={Coated FOGRA39 (ISO 12647-2:2004)}`.
Just as a comment, almost three years ago feels like ancient in ConTeXt releases. (I mean, without checking, I cannot tell for sure that LMTX was available back then [sorry, I won’t check that].)
2. I checked on the internet re colorprofile files and it tells me that I can download Coated_Fogra39L_VIGC_300.icc as an icc version that is commonly used by Adobe and I feel sure it would be sufficient for my printer's purposes. I placed it where the other profile files are located in the ConTeXt tree /context/tex/texmf-context/colors/icc/profiles This works (I have to do it myself), as long as:
1. You may place the .icc file in %USERPROFILE%/texmf/texmf-local/ (using Windwos or $HOME/texmf/texmf-local/ in Unix [Linux or macOS]).
2. You need to rename it (or make a symlink, as you prefer) to `CoatedFOGRA39.icc`, since this is the name contained in `colorprofiles.xml`.
3. You need to set you `intent` value to `Coated FOGRA39 (ISO 12647-2:2004)` (as `colorprofiles.xml` expects).
4. It worked for me (using $HOME/texmf/), but new files in the main tree may require erasing the cache and regenerating it again (`mtxrun --script cache --erase && mtxrun --generate`).
Of course, if this doesn’t work for you, please provide a minimal sample and the error message.
3. It is still not recognised, but perhaps I have to run a command for that to happen. No, you need to set the right values for the `\setupbackend` command (as for any other ConTeXt command).
My question(s):
- is my procedure correct? In other words, can I place such a file in the profiles subfolder and expect it to work? If you allow me, maybe you chain of thought needs some adjustments (in the details, where many bugs and issues live), but your expectations might have been set too high.
If a file name is used to embed a file, they have to be exactly the same (in Unix, even with case distinction [macOS may be fuzzy here]).
The same applies for intent names. (Yesterday, we found out that a profile wasn’t being loaded because of a missing comma after the closing parenthesis [“it’s in the details”].)
It isn’t a mantra, please provide a minimal sample which displays the issue you are facing. Again, this increases the probability of getting a reply. You may also have the issue with your own code or it may be that only that code hits a bug in ConTeXt.
I hope it helps,
Pablo ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___________________________________________________________________________________
On 6/15/25 11:49, jbf wrote:
Pablo, let me respond to each of the items below: [...] So I assume that my difficulty initially was to omit the curly brackets, or that I placed an abbreviated statement, just Coated FOGRA39. I do not know why the log then tells me 'omitting reference to...', but perhaps this is not a problem.
Hi Julian, I think that omiting means that ConTeXt isn’t embedding the profile (because its file cannot be found).
Or maybe the problem was that I thought I did not also need to include (ISO 1267-2:2004). I thought that was simply a descriptor and not necessary. So perhaps I needed to complete the whole statement, namely {Coated FOGRA39 (ISO 12647-2:2004)}.
AfaIk, intents need full names to (in that version) choose which file to embed. I haven’t tested the following (since defining an output intent is more than just embedding an .icc file in the final PDF document), but `intent=CoatedFOGRA39.icc` may do the trick here. But the following might work if and only if file name is exactly the above one (otherwise, the extra info needed from `colorprofiles.xml` will not be included in the final PDF document).
2. Are you also saying that {ISO Coated v2 etc.} is exactly the same?
I don’t think they are not the same file (I won’t test it, but I only consider data or files being the same when they have the same SHA512 value). Both com from the same ISO standard (ISO 12647-2:2004), but v2 or amendment 1 seems to suggest a newer version (or it might be a more particular approach to color profiling). Would file `ISOcoated_v2_300_eci.icc` fit your printer needs and/or expectations? Sorry, I don’t have any means to know.
4. Be assured that the 2022 version is LMTX and that it has worked without difficulty for me. I also have a most recent version sitting on the computer, but until I am sure that I have resolved this 'intent' issue, I do not want to switch.
Do as you please, but once you switch, you may have to find out how output intents work in newer versions after https://www.pragma-ade.com/general/manuals/standards.pdf#search=intent.
To be honest, I have looked in the 'profiles' folder of the latest version and I did not see the Coated FOGRA39 file. Hence my hesitation. The folder contains eight *.icc profile files, none of them FOGRA. (but see further on in 5. below)
Color profiles (as far as I know) are only the .icc files. `colorprofiles.xml` includes the extra info to include their information (even when not embedding the actual .icc file in the final PDF document).
5. I will have to read your comments more carefully about my downloaded file (if indeed I now still need it, perhaps not) so I can understand what you have said. I am a Linux user.
I think you need it. So, please, the following: 1. `mv -i wherever_it_is/Coated_Fogra39L_VIGC_300.icc ~/texmf/texmf-local`. 2. `ln -s ~/texmf/texmf-local/Coated_Fogra39L_VIGC_300.icc ~/texmf/texmf-local/CoatedFOGRA39.icc`. 3. `mtxrun --script cache --erase && mtxrun --generate`. 4. Compile the sample I sent in my previous message and confirm that intent isn’t ommited. 5. Do the same with your own file.
[...] It would seem to have resolved my problem, other than the fact that I don't understand the implications when its says 'omitting reference to profile for intent...'. Does that mean that the whole things wasn't really all that important in the first place??
I don‘t know whether the lack of embedd .icc file will cause any issue (since this is exactly what it happens with current latest), but I wouldn’t bet on that.
You are a very patient person, Pablo, and I am grateful for that!
(As I guess it happens with anyone,) this holds only to a certain extend. I may be pattient, but in any case I don’t have all the time in the world (as anyone else, I’m afraid). As for the lack of sample file, please consider this (that I just realized). Unless I state it clearly, I always test source files before giving any reply. In your case, I had to replace my regular standalone (current latest) with the oldest I have on my computer (setting back again and replacing it again to finally setting back to current latest). I had to find myself a minimal sample which I started testing with the older version. How do I know that .icc profiles are embedded in PDF documents generated from older versions and not with newer ones? Well, the only way I know is to uncompress the resulting PDF file and read the code (which I minmally understand). In any case, reading this from the ConTeXt source (.mkxl or .lmt files) is not an option for me (also because there may be issues elsewhere preventing a particular snippet of code working properly). I don’t have the sligthest doubt of your gratitute and your interest in solving this issue. But please, confirm that the previous five steps (in reply to #5 from your previous reply) work or tell us which error messages you get (and send another minimal sample, if the one I sent in my previous reply doesn’t show the issue). I think that these five steps may really fix the issue with the embedding of the color profile (as they have fixed it for me).
I will send the PDF file from this to the printers and assume that all is well!
Consider that this might not be the case. Please, test first the five simple steps answering to item #5 from your reply. I don’t have any experience with sending files to printers (I’m only an average user), but it should make sense to be able to send to the printers a single page sample to test whether what they receive is something that makes sense to their machines (so to speak). Sorry, but related to lacking all the time in the world, I hope tomorrow afternoon is the next time I sit in front of this computer (where I check all messages from this mailing list). I hope it helps, Pablo
Thanks Pablo, I can confirm that intent=CoatedFOGRA.icc does not work but that intent={Coated FOGRA39 (ISO 12647-2:2004)} does work, or to put it another way, the log file says profile specification 'Coated FOGRA39 (ISO 12647-2:2004)' loaded....from colorprofiles.xml. Of course, I am still unsure why the next line in the log says 'omitting reference to profile for intent 'Coated FOGRA39 (ISO 12647-2:2004)' given that it has already told me it was loaded. But at least I am now clear that the full name needs to be included in the intent statement, and that if there are spaces involved, it has to be between curly brackets {}. I can ask my printers if ISOCoated_v2_300_eci.icc fits their specifications, but given that they have already told me they want the FOGRA39, I prefer to directly follow their advice, and besides I am not in a position at the moment to be able to ask them. What I have done is to forward the PDF with the FOGRA39 intent and they have already told me that it is sufficient, and that if anything is not correct they are able to make their own internal adjustments. Which kind of solves my immediate problem, as it only really matters in a production context, where specifications have to be adhered to. The most comforting line in the PRAGMA document you referred me to is “Of course you can wonder if that all makes sense: let the printing company take care of that”! My texmf-local is directly under /tex, not under /texmf, so I made the relevant change to the terminal command and ran it using the full path /home/julian/bin/context/tex/texmf-context/tex/texmf-local. I have moved the *icc file into texmf.local successfully enough. I ran the link command and then the erase cache and generate commands. The result for BOTH your test sample, and for the other file I am working with is the same, namely backend > profiles > profile specification 'Coated FOGRA39 (ISO 12647-2:2004)' loaded from '/home/julian/bin/context/tex/texmf-context/colors/icc/context/colorprofiles.xml' backend > profiles > omitting reference to profile for intent 'Coated FOGRA39 (ISO 12647-2:2004)' But if my printers are happy to make their own adjustments, then I presume I need do no more. And much like yourself, I now have other pressing demands and will have to leave the matter rest for now. Thank you once again, Julian On 16/6/25 02:49, Pablo Rodriguez via ntg-context wrote:
On 6/15/25 11:49, jbf wrote:
Pablo, let me respond to each of the items below: [...] So I assume that my difficulty initially was to omit the curly brackets, or that I placed an abbreviated statement, just Coated FOGRA39. I do not know why the log then tells me 'omitting reference to...', but perhaps this is not a problem. Hi Julian,
I think that omiting means that ConTeXt isn’t embedding the profile (because its file cannot be found).
Or maybe the problem was that I thought I did not also need to include (ISO 1267-2:2004). I thought that was simply a descriptor and not necessary. So perhaps I needed to complete the whole statement, namely {Coated FOGRA39 (ISO 12647-2:2004)}. AfaIk, intents need full names to (in that version) choose which file to embed.
I haven’t tested the following (since defining an output intent is more than just embedding an .icc file in the final PDF document), but `intent=CoatedFOGRA39.icc` may do the trick here.
But the following might work if and only if file name is exactly the above one (otherwise, the extra info needed from `colorprofiles.xml` will not be included in the final PDF document).
2. Are you also saying that {ISO Coated v2 etc.} is exactly the same? I don’t think they are not the same file (I won’t test it, but I only consider data or files being the same when they have the same SHA512 value).
Both com from the same ISO standard (ISO 12647-2:2004), but v2 or amendment 1 seems to suggest a newer version (or it might be a more particular approach to color profiling).
Would file `ISOcoated_v2_300_eci.icc` fit your printer needs and/or expectations? Sorry, I don’t have any means to know.
4. Be assured that the 2022 version is LMTX and that it has worked without difficulty for me. I also have a most recent version sitting on the computer, but until I am sure that I have resolved this 'intent' issue, I do not want to switch. Do as you please, but once you switch, you may have to find out how output intents work in newer versions after https://www.pragma-ade.com/general/manuals/standards.pdf#search=intent.
To be honest, I have looked in the 'profiles' folder of the latest version and I did not see the Coated FOGRA39 file. Hence my hesitation. The folder contains eight *.icc profile files, none of them FOGRA. (but see further on in 5. below) Color profiles (as far as I know) are only the .icc files. `colorprofiles.xml` includes the extra info to include their information (even when not embedding the actual .icc file in the final PDF document).
5. I will have to read your comments more carefully about my downloaded file (if indeed I now still need it, perhaps not) so I can understand what you have said. I am a Linux user. I think you need it. So, please, the following:
1. `mv -i wherever_it_is/Coated_Fogra39L_VIGC_300.icc ~/texmf/texmf-local`. 2. `ln -s ~/texmf/texmf-local/Coated_Fogra39L_VIGC_300.icc ~/texmf/texmf-local/CoatedFOGRA39.icc`. 3. `mtxrun --script cache --erase && mtxrun --generate`. 4. Compile the sample I sent in my previous message and confirm that intent isn’t ommited. 5. Do the same with your own file.
[...] It would seem to have resolved my problem, other than the fact that I don't understand the implications when its says 'omitting reference to profile for intent...'. Does that mean that the whole things wasn't really all that important in the first place?? I don‘t know whether the lack of embedd .icc file will cause any issue (since this is exactly what it happens with current latest), but I wouldn’t bet on that.
You are a very patient person, Pablo, and I am grateful for that! (As I guess it happens with anyone,) this holds only to a certain extend. I may be pattient, but in any case I don’t have all the time in the world (as anyone else, I’m afraid).
As for the lack of sample file, please consider this (that I just realized). Unless I state it clearly, I always test source files before giving any reply.
In your case, I had to replace my regular standalone (current latest) with the oldest I have on my computer (setting back again and replacing it again to finally setting back to current latest).
I had to find myself a minimal sample which I started testing with the older version.
How do I know that .icc profiles are embedded in PDF documents generated from older versions and not with newer ones?
Well, the only way I know is to uncompress the resulting PDF file and read the code (which I minmally understand). In any case, reading this from the ConTeXt source (.mkxl or .lmt files) is not an option for me (also because there may be issues elsewhere preventing a particular snippet of code working properly).
I don’t have the sligthest doubt of your gratitute and your interest in solving this issue. But please, confirm that the previous five steps (in reply to #5 from your previous reply) work or tell us which error messages you get (and send another minimal sample, if the one I sent in my previous reply doesn’t show the issue).
I think that these five steps may really fix the issue with the embedding of the color profile (as they have fixed it for me).
I will send the PDF file from this to the printers and assume that all is well! Consider that this might not be the case.
Please, test first the five simple steps answering to item #5 from your reply.
I don’t have any experience with sending files to printers (I’m only an average user), but it should make sense to be able to send to the printers a single page sample to test whether what they receive is something that makes sense to their machines (so to speak).
Sorry, but related to lacking all the time in the world, I hope tomorrow afternoon is the next time I sit in front of this computer (where I check all messages from this mailing list).
I hope it helps,
Pablo ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist :ntg-context@ntg.nl /https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage :https://www.pragma-ade.nl /https://context.aanhet.net (mirror) archive :https://github.com/contextgarden/context wiki :https://wiki.contextgarden.net ___________________________________________________________________________________
On 6/16/25 01:35, jbf wrote:
Thanks Pablo,
I can confirm that intent=CoatedFOGRA.icc does not work but that intent={Coated FOGRA39 (ISO 12647-2:2004)} does work, or to put it another way, the log file says profile specification 'Coated FOGRA39 (ISO 12647-2:2004)' loaded....from colorprofiles.xml.
Sorry for not having replied before, Julian.
Of course, I am still unsure why the next line in the log says 'omitting reference to profile for intent 'Coated FOGRA39 (ISO 12647-2:2004)' given that it has already told me it was loaded.
I tried to describe that (from what I saw when briefly inspecting the code from the generated PDF document). I will try to describe it again: The most obvious (missing) thing is the lack of the embedded profile (file `Coated_Fogra39L_VIGC_300.icc`). Since I was able to replicate that error and then I fixed it (landing `Coated_Fogra39L_VIGC_300.icc` embedded in the PDF document), I think your distribution isn’t being capable to find that file. But I haven’t tested whether the omission also failed to include other info (such as [so to speak] relevant tags) in a way that your printers may have problems to print your PDF documents.
My texmf-local is directly under /tex, not under /texmf
Sorry for taking that for granted. Standalone comes with `~/tex/texmf-local`. But one may create another `~/texmf/texmf-local/` (and for fonts with `~/texmf/texmf-fonts`). Which is the gain of that? If you have three different standalones on your user, such as `$HOME/production-context`, `$HOME/latest-context` and `$HOME/older-context`, the way to have a common `texmf-local` or `texmf-fonts` is under `$HOME/texmf/`. I hope it is clearer now. Of course, nothing prevents you from using `texmf-local` from each standalone, but I think the other approach may be more convenient.
[...] I have moved the *icc file into texmf.local successfully enough. I ran the link command and then the erase cache and generate commands.
If the link is working, I don’t know what is (or what I’m) missing here. But since this worked for me, I have the impression that your standalone is having issues to find the .icc file.
But if my printers are happy to make their own adjustments, then I presume I need do no more. And much like yourself, I now have other pressing demands and will have to leave the matter rest for now.
I apologize for that, I realized now that my previous looks like I’m blaming you for wasting my time. If that were the case (which wasn’t), I’m the only one responsible for wasting my time. What I should have described clearly is how I deal when replying to others who share issues they may have with ConTeXt. [Julian, what comes next is written in general, not specially related to this thread. Please, don’t read it as personally directed to you, because it isn’t at all.] My three main steps are: 1. Find out what is the experienced issue at stake. 2. Try to analyze what is going on with the issue. 3. Either compose a reply with a solution or try report the issue as a potential bug. As for 2 and 3, it is pretty straightforward to know whether I can do it or not. With 1, when the user gives no sample, everything is guesswork (at least, in my case). A sample given by the user makes testing much faster (and also the finding of an issue or a highly probable solution). [Back to you again, Julian.] With your case, I was concerned since it wasn’t clear to me that the code you might be getting wouldn’t end up being problematic for your printers (and in the end leading to money loss [no matter how big]). I also had the impression that you might be thinking that things were better than (I thought, probably) they really were. Of course, I wanted your files and profiles to go well, but I couldn’t even write that they weren’t consistent with what ConTeXt was supposed to output. In any case, I hope everything went well with the documents. Pablo
Indeed, Pablo, everything went well and the printers are happy with what they got. I did a lot of experimentation with different things (won't bore you with all that), using both my 2022 version and the more or less latest 2025... discovered, among other things that the 2022 version is much more forgiving in this area, so clearly later versions of ConTeXt have tightened things up. But one difference is that if I put intent=default in when using the 2022 version, it complains immediately that it can't recognise it... and that is true, because it the colorprofile.xml does not include that. Using a 2025 version, intent=default gives a whole range of possibilities: backend > profiles > profile specification 'sRGB-v4.icc' loaded from '/home/julian/data/context/tex/texmf-context/colors/icc/context/colorprofiles.xml' backend > profiles > setting 'sRGB-v4.icc' as default 'rgb' color space backend > profiles > profile specification 'CGATS001Compat-v2-micro.icc' loaded from '/home/julian/data/context/tex/texmf-context/colors/icc/context/colorprofiles.xml' backend > profiles > setting 'CGATS001Compat-v2-micro.icc' as default 'cmyk' color space backend > profiles > profile specification 'sGrey-v4.icc' loaded from '/home/julian/data/context/tex/texmf-context/colors/icc/context/colorprofiles.xml' backend > profiles > setting 'sGrey-v4.icc' as default 'gray' color space backend > profiles > setting output intent to 'sRGB v4 Minimal' with id 'Custom' for entry 1 Now, while the cmyk colorspace does not happen to be the FOGRA39 one, my printers tell me that they can easily make the adjustment themselves, but they also had no difficulty with what I sent them as a product produced by the 2022 version where I had used SWOP2006_Coated3v2.icc, so in other words they made their own internal adjustments without difficulty, which effectively resolved my problem. Maybe I caused myself a 'storm in a teacup' as the saying goes. But I suppose what I was trying to do, in addition to resolving something that might have meant loss of money, was to actually understand what is going on in this area. Your explanations have been most helpful in this regard, though I still confess it is all a bit too confusing for me, due to my lack of knowledge. In my internet 'reasearch' I discovered that it is equally as confusing for many others in a range of other programs other than ConTeXt. I think we can leave the matter to rest for now. Julian On 19/6/25 05:09, Pablo Rodriguez via ntg-context wrote:
In any case, I hope everything went well with the documents.
participants (2)
-
jbf -
Pablo Rodriguez