3 ms·
It doesn't have to be accurate. Anything close is better than black.
by superchroma 4y ago
It doesn't have to be accurate. Anything close is better than black.
- traceroute66 4y ago> It doesn't have to be accurate. Anything close is better than black. No. Because that breaks design intent. If the client and designer agree on "Pantone XYZ", then you can't just go replacing that with "something that looks vaguely like Pantone XYZ". That would be a breach of the agreement between client and designer. It would also, as explained further up this thread, "its not that easy". "Pantone XYZ" is not "just another name for C:1,M:2,Y:3,K:4", its all about ensuring consistent reproduction of that colour across all desired substrates.
- probably_wrong 4y agoHow about letting the user choose? Because if Adobe stopped acting like they know better they could solve this with one click: > You are using Pantone colors, but you don't have a license for them. > [X] Replace with a similar CMYK value, obtained from printing the color in Bob's old home printer. > [ ] Purchase rights to the Pantone library. Now the x% of designers who really need Pantone colors can pay for them and the remaining (100-x)% users can use their files in peace. This is similar to what Inkscape does when converting a PDF with unknown fonts, and it's (IMO) a much better solution.
- superchroma 4y agoThe point is not to get it almost right, the point is to not maim the file by turning everything black so you can't see anything and have to start from zero. Obviously the file is damaged either way, but we can do a hell of a lot better than all color data eliminated altogether.