HEX numbers used in HTML for the web typically assume an sRGB (the default), so that's the profile you want your apps/document to be assigned even before you convert to CMYK.Īs for the the CMYK side, you can assign a "typical" CMYK profile in your apps/document, but which one to use? Are you printing to a coated paper or an uncoated paper are you printing using offset inks or inkjet inks, etc etc etc. For you to set up a consistent conversion you need to set your apps/documents Colour Settings to match what you expect to see on the web. if its being used in an sRGB workspace or an AdobeRGB workspace, etc. FF0000 = 255R 0G 0B = Red, and even these will look different in different RGB workspaces e.g. But if you were give a bunch of HEX codes first, with no cross reference to a Pantone colour, you're guess is as good as What you need to remember is that HEX codes (and RGB) are just a set of numbers. Since you are talking about a branding situation, and you want to specify standard HTML codes, you can always standarize based on Pantone's published values. In reverse, there isn't necessarily a good way to reverse-match in Pantone ink to any HEX/RGB colour. Your opinion might be different, and your apps, depending on the colour management settings, will see it differently, too. Pantone's HEX values are based on their opinion as to what their Pantone 165 will look in sRGB mode. Any colorspace used in the digital word, be it RGB or, worse, CMYK is a much smaller colorspace, so any HEX/RGB, whether Pantone defines it or not, amounts to the "closest" match to that Lab measurement in that colorspace. Hence, The Pantone spot libraries used in apps are based on an actual reading of that ink colour on a printed page using a spectrophotometer, measured in the Lab colorspace (which includes the range of all spectral light a human eyey can generally perceive). A Pantone spot colour (as mentioned before) is an actual custom mixture of ink.
0 Comments
Leave a Reply. |