Re: [Gimp-developer] GIMP-2.10 and GIMP2.99 are still sRGB-only image editors
On Fri, Feb 5, 2021 at 3:00 AM Elle Stone wrote: > Participating in GIMP development used to be challenging and enjoyable. > But over the last couple of years my interest in and patience with the > slow pace of progress regarding GIMP color management have dwindled to > the point of disappearing altogether. Two years ago we had three active developers hacking on GIMP like there was no tomorrow. We lost one of them entirely, it seems, and another one is mostly preoccupied with family business, so we are down to one active developer and a few new active contributors. We are also approaching the end of very long and tiresome work on refactoring which is not done yet. Also, a lot of time of that one active developer was spent figuring out ways to make development of GIMP sustainable (no details at this point in time, sorry). So yes, there are several critical areas where help is needed. Color management is clearly one of them. I guess if you adjust your expectations accordingly, you will see that there is no acting in bad faith here. Alex ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] creating a mac dmg for 2.99
Hello all, I’m interested in compiling the dev branch code and becoming the hosting developer for the eventual 3.0 release of the Gimp for Mac. I need to understand the steps for creating this as they have been in the past. What pitfalls should I look out for? Please advise / point in the right direction Thank you. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] [Gimp-user] GIMP-2.10 and GIMP2.99 are still sRGB-only image editors
On 2/4/21 7:14 PM, Michael Schumacher via gimp-user-list wrote: On February 5, 2021 12:59:50 AM GMT+01:00, Elle Stone wrote: I was able to write code that fixed some of the bugs I reported for GIMP-2.99 color management. But once I reached the point where further coding requirements exceeded my coding ability, progress simply stopped, with everyone else saying "some day" proper color management for GIMP would be a priority. I began to feel like the best way to make sure a bug would never get fixed, was to have the dreaded "Concepts: Color Science" tag attached to it. You make it sound like introducing this tag was a wrong decision. As I introduced it as a way to group thhese issues together, did I do something wrong there? Of course you didn't do anything wrong. It's an excellent tag to let people know what the topic is. It's been stated over and over again by a particular GIMP dev that GIMP development works best if people do what they are interested in doing. The question is which current GIMP devs other than myself have an *interest* in dealing bugs tagged with "Concept: Color Science"? It would be great if you could find the time to go through the links I provided in my post and add the tag as appropriate to any relevant bug reports that don't yet have the tag. Someday when GIMP has found another developer with an interest in color management and color science, that person will find the "Concepts: Color Science" tag very useful. Best, Elle ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] GIMP-2.10 and GIMP2.99 are still sRGB-only image editors
On Thu, 2021-02-04 at 18:59 -0500, Elle Stone wrote: > > GIMP-2.10 does *NOT* produce correct editing results in color spaces > other than sRGB. Neither does GIMP-2.99. For sure you also get a dramatically bad result if you export as png of jpeg from 32-bit images. But convert to 8-bit first and it's OK. So clearly there's work to be done. It might be that the attention Web browser makers are currently giving to other colourspaces, wider gamut, and higher bit depth, will drive demand - and, we can hope, lead to increased resources for GIMP too. There are other areas where GIMP needs work, too - one of my own interests is in text and better openType support for example - so we are both in the same position in that that's more we'd like to see than we can do. In my case i'm slowly doing experiments, but no patches (yet?). In your case you're well ahead of me but the patches are very hard to review, because colour management is so specialized. Maybe the right conversation to have is, how can we get some more programmers to spend their free time on GIMP. [replying only to gimp-developer list, not user list as well] -- Liam Quin - web slave for https://www.fromoldbooks.org/ Full-time slave in voluntary servitude ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] [Gimp-user] GIMP-2.10 and GIMP2.99 are still sRGB-only image editors
On February 5, 2021 12:59:50 AM GMT+01:00, Elle Stone wrote: >I was able to write code that fixed some of the bugs I reported for >GIMP-2.99 color management. But once I reached the point where further >coding requirements exceeded my coding ability, progress simply >stopped, >with everyone else saying "some day" proper color management for GIMP >would be a priority. I began to feel like the best way to make sure a >bug would never get fixed, was to have the dreaded "Concepts: Color >Science" tag attached to it. You make it sound like introducing this tag was a wrong decision. As I introduced it as a way to group thhese issues together, did I do something wrong there? -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] GIMP-2.10 and GIMP2.99 are still sRGB-only image editors
A misconception I keep seeing on various forums needs to be corrected: GIMP-2.10 does *NOT* produce correct editing results in color spaces other than sRGB. Neither does GIMP-2.99. Editing in AdobeRGB, ProPhotoRGB, Rec2020, etc WILL produce *wrong* results for many operations, and unless you are thoroughly conversant with the underlying code, or else have a way to compare results with a properly color-managed editing application, you don't have any way to know what's right and what's wrong. It's best to stick with editing only in GIMP's built-in sRGB color spaces. The same is true if you are using GIMP-2.99: Some things that don't work in GIMP-2.10, do work in GIMP-2.99. Other things that actually do work in GIMP-2.10, don't work in GIMP-2.99. About two years ago major changes were made in babl and additional changes were made in GIMP-2.99, messing up stuff that still works in GIMP-2.10. For awhile progress was being made in GIMP-2.99 on extending the arena of "what actually works", some of which progress is from bug reports I filed and in some cases helped to fix - it seems nobody else was testing the new code to see what actually did work. I was able to write code that fixed some of the bugs I reported for GIMP-2.99 color management. But once I reached the point where further coding requirements exceeded my coding ability, progress simply stopped, with everyone else saying "some day" proper color management for GIMP would be a priority. I began to feel like the best way to make sure a bug would never get fixed, was to have the dreaded "Concepts: Color Science" tag attached to it. Since autumm of 2013 I've been participating in GIMP development, mostly in the area of color management (editing in color spaces other than sRGB) and color science (making sure GIMP code produces correct results for things like layer blend modes, Curves and Levels, AutoStretch, Luminance, and so on; and adding code for things like LCh color pickers and blend modes). Participating in GIMP development used to be challenging and enjoyable. But over the last couple of years my interest in and patience with the slow pace of progress regarding GIMP color management have dwindled to the point of disappearing altogether. If someone else feels like helping with GIMP color management and color science, here's a list of still-open bug reports that I reported after the migration to gitlab, most of which have to do with color management/color science: https://gitlab.gnome.org/GNOME/gimp/-/issues?scope=all=%E2%9C%93=opened_username=ellestone Here are bugs that I opened before the migration to gitlab: https://gitlab.gnome.org/GNOME/gimp/-/issues?scope=all=%E2%9C%93=opened_username=bugzilla-migration=ellestone The most important color management bugs still open from before the migration to gitlab are these: * Replace hard-coded sRGB parameters to allow editing in other RGB working spaces (opened 6 years ago): https://gitlab.gnome.org/GNOME/gimp/-/issues/594 - in some ways this bug is obsolete as current GIMP color management issues are less about actual hard-coded values and more about a lack of any way to convey the required "not sRGB" color space information to various sections of code that need this information. * Decomposed to LAB images have the wrong ICC profile assigned (opened 4 years ago): https://gitlab.gnome.org/GNOME/gimp/-/issues/883 * Address various limitations of LCMS soft proofing (opened 4 years ago): https://gitlab.gnome.org/GNOME/gimp/-/issues/976 the and hoping very much that GIMP will find new developers that them a lot of energy and some interest and expertise in color management and color science. * Support for high bit depth RGB (and LCH?) color palettes for painting (opened 2 years ago): https://gitlab.gnome.org/GNOME/gimp/-/issues/1328 Similar searchs in https://gitlab.gnome.org/GNOME/gegl/ and https://gitlab.gnome.org/GNOME/babl/ will turn up a few additional color management issues. Best of luck to all, Elle Stone -- https://ninedegreesbelow.com Color management and free/libre photography ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Please review my patch
Speaking of patches that need to be committed, here's a bug that's had a patch attached to it for over a year: https://gitlab.gnome.org/GNOME/gimp/-/issues/3471 My patch for #3471 does work and should be committed - the current code is clearly wrong - luma lighten and luma darken blend modes have been giving wrong results for a very long time. On 2/1/21 1:55 PM, Elle Stone wrote: My last comment in https://gitlab.gnome.org/GNOME/gimp/-/issues/2933 is: "Could someone please review this patch? It works. . . . This is a year old bug that could be fixed if someone would just commit the code. The corresponding bug in GEGL hue-chroma has been fixed - maybe we could get this fixed also in GIMP? Maybe even in GIMP-2.10?" #endquote Seven months later still nobody has reviewed the patch. A similar bug report, almost certainly the exact same bug - can't see how it could be anything else - was filed recently: https://gitlab.gnome.org/GNOME/gimp/-/issues/6308 to which bug report a request for "Additional Diagnostics" was attached. The requested "Diagnostics" were available 8 months ago in bug #2933. It's a matter of precision. The "EPSILON" value used in the layer blend code is too small to eliminate unavoidable rounding errors in the LCh Chroma code. I attached an updated patch to the new bug report. The update doesn't change the actual code that fixes the problem - it just allows the patch to be applied to the affected layer blend file given other recent changes to the file. I can guess the response from other devs as to why nobody has taken the time to review my patch: Other priorities, too few developers, too much to do, nobody else has color management or color science as a top priority. I do understand the problem of too few devs, but if one of the GIMP devs could take it upon themselves to finally get around to checking my patch, then three bug reports could be closed: the two mentioned above and also https://gitlab.gnome.org/GNOME/gimp/-/issues/2934 - leastways I'm pretty sure the latter bug is also fixed - none of these three bugs affect the already-patched version of GIMP that I use for editing. I had totally forgotten about bugs #2933 and #2934 (which I filed a year ago) until bug #6308 was filed. There's nothing else I can do about these bugs. I don't have - and don't want - commit rights to GIMP code. Some other GIMP dev needs to actually check the patch and decide it works and then apply it. Regards, Elle -- https://ninedegreesbelow.com Color management and free/libre photography ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Translating Gimp into arabic
Gimp already has Arabic translations. Do you have something specific in mind? On 03/02/2021 09:41, Abdullah OLABI wrote: Hi, Hope you are all fine. I would like please to talk to someone in your organisation about translating Gimp into Arabic language. With kind regards Abdullah Olabi ___ gimp-developer-list mailing list List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Translating Gimp into arabic
Hi, Hope you are all fine. I would like please to talk to someone in your organisation about translating Gimp into Arabic language. With kind regards Abdullah Olabi ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
