3 ms·
Naive question perhaps: why was CMYK so hard to add to Gimp? Was it because non RGB color spaces were hard, due to the program being designed around RGB and th
by alkonaut 4y ago
Naive question perhaps: why was CMYK so hard to add to Gimp?
Was it because non RGB color spaces were hard, due to the program being designed around RGB and the assumption of RGB is everywhere in the codebase?
Or is it something particularly tricky about CMYK?
- prokoudine 4y agoFirst off, the work is not complete yet. E.g. there is no CMYK image mode. You can open a CMYK image with automatic conversion to sRGB, you can also do a soft-proof, and you can export CMYK images (JPEG, TIFF, PSD). This part is comparatively cheap to do, but it needed some infrastructure in place and, above all, it needed someone to write the code. The previous attempt to add CMYK exporting didn't go well. The developer implemented all that in a new set of plugins instead of building the functionality into existing code. This wouldn't work. The developer apparently wasn't interested to do it right or did not have the time, he wouldn't say. So there's the architectural aspect of this and then there's availability of a contributor willing to hacks on this. You can read a little more about this GSoC project here: https://www.gimp.org/news/2022/06/03/cmyk-in-gsoc-2022/ https://www.gimp.org/news/2022/06/03/cmyk-in-gsoc-2022/
- vasco 4y ago> The developer apparently wasn't interested to do it right or did not have the time, he wouldn't say Bit weird to put it like that, everyone else in the world didn't do it either, it's open source after all.
- prokoudine 4y agoJust stating the fact. I'm fine with that. I still appreciate the effort.
- deleted 4y ago[deleted]
- hitekker 4y agoAgreed. Insinuating "other developers are careless" sounds odd given how GIMP lost their own wiki. https://gitlab.gnome.org/Infrastructure/gimp-web/-/issues/257 https://gitlab.gnome.org/Infrastructure/gimp-web/-/issues/25... Years of docs gone because one unnamed maintainer forgot to update hosting. With no backups. The official roadmap https://wiki.gimp.org/wiki/Roadmap#GIMP_3.0 https://wiki.gimp.org/wiki/Roadmap#GIMP_3.0 has been inaccessible for 3 months, which the blog glosses over as no big deal. This kind of amateurism is uncommon to Blender and Krita but rather common to GIMP; some of their maintainers have even been banned from twitter.
- prokoudine 4y ago> Insinuating "other developers are careless" OMG, nope. The person in a parent thread asked a very specific question: what's tricky about CMYK support and why it didn't come earlier. How can I answer that without explaining that CMYK exporting almost happened years before and saying what went wrong there? Of course, it's your choice to think the worst of people. > some of their maintainers have even been banned from twitter. Are you referring to me?
- app4soft 4y ago> Naive question perhaps: why was CMYK so hard to add to Gimp? Not only for Gimp, but for Inkscape too.[0,1] [0] https://wiki.inkscape.org/wiki/Color_Management_Planning https://wiki.inkscape.org/wiki/Color_Management_Planning [1] https://inkscape.org/cs/forums/beyond/cmyk-support/ https://inkscape.org/cs/forums/beyond/cmyk-support/
- phkahler 4y agoI thought GEGL was taking care of most of the work for CMYK years ago, but I don't GIMP so that wasn't so.
- resoluteteeth 4y agoI also assumed they had finished it because I think they started working on it like 25 years ago
- stuaxo 4y agoone part was (and is) to port all the existing plugins.
- ape4 4y agoWhy wouldn't it be hard - its the central part of how a imagine editor works.