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 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 ___________________________________________________________________________________