[Gimp-developer] Documentation on color spaces
The topic of Documentation came up recently. It occurred to me that existing and future Gimp developers might find documentation on color spaces and ICC profiles helpful. So I wrote up a Completely Painless Programmer's Guide to XYZ, RGB, ICC, xyY, and TRCs, which is posted on my website at http://ninedegreesbelow.com/temp/xyz-rgb.html. If my Guide seems useful to developers, I'll put the content under an applicable license so it can be hosted elsewhere and modified by other people. In the meantime, if anyone would like to read it and give feedback, corrections, suggestions, I'll edit the Guide to make it more clear, more useful, etc (if nobody is interested, that's OK too!). If there's an interest, I'll put together Part 2, which would cover: * CieLAB (how it relates to XYZ and why it's useful for image editing) * CMY(K) (how it relates to RGB and XYZ) * YCbCr, YUV, HSL, and HSV (how these derivative color spaces are connected to their parent RGB color space) * LCMS2 (how it links working space profiles with monitor, camera, and printer profiles) Elle -- Elle Stone http://ninedegreesbelow.com Just because it's a standard, doesn't mean it's right. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] GIMP requires the GEGL operation gegl:over.
please add me in the reply to as i am not part of the DG. i am compiling from source using git. i compile babl,gegl and gimp from git repositories. for the last 5 compile i get this error on concole: (gimp:11790): GEGL-gegl-operations.c-WARNING **: Adding GeglChantinvert-linear_c shadows GeglChantinvert_c for operation gegl:invert and then this popup: GEGL operation missing! GIMP requires the GEGL operation gegl:over. This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for GIMP. i cannot find a solution to this in google. can you help? -- Regards, Adi Spivak IT Manager 17 HaYetzira St, Mordot HaCarmel Industrial Park, Yokneam Elite Mail: P.O Box 687, Yokneam 20692. Israel TelFax.: (+972) 48-290-124. (+972) 48-290-100 www.fit-pc.com www.compulab.co.il ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Documentation on color spaces
Please do. Very interesting, not only for developers. Onkel Hatti - Original Message - Subject: [Gimp-developer] Documentation on color spaces Date: Wed, 9 Oct 2013 09:20:46 -0400 From: Elle Stone l.elle.st...@gmail.com The topic of Documentation came up recently. It occurred to me that existing and future Gimp developers might find documentation on color spaces and ICC profiles helpful. So I wrote up a Completely Painless Programmer's Guide to XYZ, RGB, ICC, xyY, and TRCs, which is posted on my website at http://ninedegreesbelow.com/temp/xyz-rgb.html. If my Guide seems useful to developers, I'll put the content under an applicable license so it can be hosted elsewhere and modified by other people. In the meantime, if anyone would like to read it and give feedback, corrections, suggestions, I'll edit the Guide to make it more clear, more useful, etc (if nobody is interested, that's OK too!). If there's an interest, I'll put together Part 2, which would cover: * CieLAB (how it relates to XYZ and why it's useful for image editing) * CMY(K) (how it relates to RGB and XYZ) * YCbCr, YUV, HSL, and HSV (how these derivative color spaces are connected to their parent RGB color space) * LCMS2 (how it links working space profiles with monitor, camera, and printer profiles) Elle -- Elle Stone http://ninedegreesbelow.com Just because it's a standard, doesn't mean it's right. ___ gimp-developer-list mailing list List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/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
Re: [Gimp-developer] GIMP requires the GEGL operation gegl:over.
On 10/07/2013 10:23 AM, Adi Spivak wrote: please add me in the reply to as i am not part of the DG. i am compiling from source using git. i compile babl,gegl and gimp from git repositories. for the last 5 compile i get this error on concole: (gimp:11790): GEGL-gegl-operations.c-WARNING **: Adding GeglChantinvert-linear_c shadows GeglChantinvert_c for operation gegl:invert and then this popup: GEGL operation missing! GIMP requires the GEGL operation gegl:over. This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for GIMP. i cannot find a solution to this in google. can you help? Remove all installed GEGL operations, do a git clean -xdf in the gegl source tree, then rebuild and install. --Mitch ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] Translator available
Hello everyone Just eanted to let you know that I am available as a translator in case you need help Spanish- english I got a 630 at the TOEFL :) Enviado desde mi iPhone ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] Mystery: scaling thin areas makes them partially transparent
I have a layer filled with black 100% opaque. If I select a 3px wide strip only shrink the long side, the final result is not 100% opaque: I get a one-pixel high black line at 100% opacity with a black line at 87% opacity on each side. And is the selected strip is only 1px high, the resulting line is 74% opaque. If thereis no alpha channel I get gray instead. This seems interpolation related since using None doesn't produce this result. Is there an explanation to this? And can it be avoided? ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Mystery: scaling thin areas makes them partially transparent
Hmm, I was going to report the same observation. A few days ago I upscaled a 768px wide gradient times 1600, but just horizontally, keeping the vertical dimension the same. There were several pixels at either side of the gradient (but not at the top and bottom edges) that were clear. Are you sure none also doesn't have the same issue? When I removed the alpha channel, I got white. On 10/9/13, Ofnuts ofn...@laposte.net wrote: I have a layer filled with black 100% opaque. If I select a 3px wide strip only shrink the long side, the final result is not 100% opaque: I get a one-pixel high black line at 100% opacity with a black line at 87% opacity on each side. And is the selected strip is only 1px high, the resulting line is 74% opaque. If thereis no alpha channel I get gray instead. This seems interpolation related since using None doesn't produce this result. Is there an explanation to this? And can it be avoided? ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list -- Elle Stone http://ninedegreesbelow.com Just because it's a standard, doesn't mean it's right. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Mystery: scaling thin areas makes them partially transparent
This is how to fix this Enhance GIMP and GEGL so that the Image Scale and Layer Scale operations use the “CLAMP” (nearest neighbour) abyss policy and the tools that use samplers use the “NONE” (fade to transparency) abyss policy. This will remove the border artifacts from the former operations without introducing “radiating extensions” to the latter. Note: Enlarging or shrinking abnormally small images is not part of the target use case. I also am not 100% sure that the above recommendation is consistent with the target use case. Also note that I committed to fix this a bit less than a year ago and that a lot of life happened in the meantime. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Mystery: scaling thin areas makes them partially transparent
On 10/09/2013 06:59 PM, Nicolas Robidoux wrote: Note: Enlarging or shrinking abnormally small images is not part of the target use case. I also am not 100% sure that the above recommendation is consistent with the target use case. Actually I found this while working on a script that does a non-affine transform by scaling successive lines of the image. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Documentation on color spaces
On 09.10.2013 at 03:20 P.M., Elle Stone wrote: The topic of Documentation came up recently. It occurred to me that existing and future Gimp developers might find documentation on color spaces and ICC profiles helpful. So I wrote up a Completely Painless Programmer's Guide to XYZ, RGB, ICC, xyY, and TRCs, which is posted on my website at http://ninedegreesbelow.com/temp/xyz-rgb.html. Indeed, it's very useful. It might surely take me some time to work through it, but thank you very much for your efforts to share your knowledge! If there's an interest, I'll put together Part 2, which would cover: * CieLAB (how it relates to XYZ and why it's useful for image editing) * CMY(K) (how it relates to RGB and XYZ) * YCbCr, YUV, HSL, and HSV (how these derivative color spaces are connected to their parent RGB color space) * LCMS2 (how it links working space profiles with monitor, camera, and printer profiles) Yes, there is interest in it (at least from me). Kind regards, Sven ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Documentation on color spaces
Hi Elle, On 09.10.2013 15:20, Elle Stone wrote: The topic of Documentation came up recently. It occurred to me that existing and future Gimp developers might find documentation on color spaces and ICC profiles helpful. So I wrote up a Completely Painless Programmer's Guide to XYZ, RGB, ICC, xyY, and TRCs, which is posted on my website at http://ninedegreesbelow.com/temp/xyz-rgb.html. I am not a developer, but this is the best text I found about this stuff up to now. Very well written. If my Guide seems useful to developers, I'll put the content under an applicable license so it can be hosted elsewhere and modified by other people. Please do that! I'll make a video from it (well, parts of it, as usual with the books also ;-) ) Rolf http://meetthegimp.org ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] GUI/Interaction Design
Hi everybody, I just wanted to publically announce that Peter Sikking (IRC guiguru/guihipster) is back on the project. Without going into details on how and why the cooperation has been difficult/stalled for quite a time, I think it's justified so make a few things clear, in order to avoid future trouble: - Most things will be like before - Peter is our interaction architect and has the say on whether a GUI is good enough for GIMP - This does *not* mean that he will just decide and things have to be developed - Everything can and will be discussed - Things happen iteratively, no design/interaction idea and no code idea is right or final on first try, if we keep that in mind, nobody has to panic - We will implement GUI things by consensus, where interaction design and development present their ideas to each other and *talk* - I mean *talk*, not playing piss games, everybody just behave reasonably and listen to each other and all will be fine That's mostly it, I'm looking forward to getting some great GUI stuff done, instead of just guessing what might be right for our users. Regards, --Mitch ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GUI/Interaction Design
On 10/09/2013 04:17 PM, Michael Natterer wrote: Hi everybody, I just wanted to publically announce that Peter Sikking (IRC guiguru/guihipster) is back on the project. Without going into details on how and why the cooperation has been difficult/stalled for quite a time, I think it's justified so make a few things clear, in order to avoid future trouble: - Most things will be like before - Peter is our interaction architect and has the say on whether a GUI is good enough for GIMP - This does *not* mean that he will just decide and things have to be developed - Everything can and will be discussed - Things happen iteratively, no design/interaction idea and no code idea is right or final on first try, if we keep that in mind, nobody has to panic - We will implement GUI things by consensus, where interaction design and development present their ideas to each other and *talk* - I mean *talk*, not playing piss games, everybody just behave reasonably and listen to each other and all will be fine That's mostly it, I'm looking forward to getting some great GUI stuff done, instead of just guessing what might be right for our users. Regards, --Mitch I don't mean to clog up the discussion, but this news deserves to be welcomed! Thank you to Peter, Mitch, and all the many others who have done such great work. I know we can't ever fully comprehend all the work and time that everybody has invested, or ever properly thank you for what you have made. So, this will have to do Thanks! Jay ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Documentation on color spaces
On 10/9/13, Rolf Steinort i...@meetthegimp.org wrote: On 09.10.2013 15:20, Elle Stone wrote: If my Guide seems useful to developers, I'll put the content under an applicable license so it can be hosted elsewhere and modified by other people. Please do that! I'll make a video from it (well, parts of it, as usual with the books also ;-) ) Rolf, can you suggest an appropriate license? Several people have said very kind things about the Guide and a couple of people think there might be a more general audience than just programmers. So perhaps I should move the Guide out of the temp folder (which is for temporary posts) and over to the photography folder, with appropriate license information at the bottom and with the reference to Gimp from git and Cairo in Figure 6 removed. I'm sure adding documentation is like adding code - it doesn't happen automagically. But if anyone wants to put (all or portions) of the Guide somewhere in Gimp documentation, I can supply a PDF or a latex file, or plain text, or whatever is convenient. And if having the Guide also on my website presents a conflict of some sort (I don't know how these things are supposed to work), I can remove the Guide from my website altogether. Several people have expressed an interest in Part 2, so writing Part 2 in on my to do list. Elle ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Mystery: scaling thin areas makes them partially transparent
There is a bug open about that : https://bugzilla.gnome.org/show_bug.cgi?id=696090 Completly forgot that one... - Mail original - De: Ofnuts ofn...@laposte.net À: Nicolas Robidoux nicolas.robid...@gmail.com, Elle Stone l.elle.st...@gmail.com Cc: gimp-developer-list@gnome.org Envoyé: Mercredi 9 Octobre 2013 19:45:46 Objet: Re: [Gimp-developer] Mystery: scaling thin areas makes them partially transparent On 10/09/2013 06:59 PM, Nicolas Robidoux wrote: Note: Enlarging or shrinking abnormally small images is not part of the target use case. I also am not 100% sure that the above recommendation is consistent with the target use case. Actually I found this while working on a script that does a non-affine transform by scaling successive lines of the image. ___ gimp-developer-list mailing list List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/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
Re: [Gimp-developer] Documentation on color spaces
On Wed, 2013-10-09 at 16:32 -0400, Elle Stone wrote: perhaps I should move the Guide out of the temp folder (which is for temporary posts) and over to the photography folder, with appropriate license information at the bottom and with the reference to Gimp from git and Cairo in Figure 6 removed. If you do that, please add a redirect, since the URL has now been posted on a public list. What you've written is incredibly useful, thank you! A couple of minor suggestions - * make references to figures and tables be links within the document * consider using HTML abbreviation/acronym/initialism markup, or just span elements with title attributes, for the abbreviations and jargon, throughout the document (yay for search and replace) or at least the first occurrence in any paragraph. Yes, keep up the good work with a part 2 :-) Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Documentation on color spaces
On 09.10.2013 22:32, Elle Stone wrote: On 10/9/13, Rolf Steinort i...@meetthegimp.org wrote: On 09.10.2013 15:20, Elle Stone wrote: If my Guide seems useful to developers, I'll put the content under an applicable license so it can be hosted elsewhere and modified by other people. Please do that! I'll make a video from it (well, parts of it, as usual with the books also ;-) ) Rolf, can you suggest an appropriate license? I release all my stuff under Creative Commons. I think CC is the best suited license for texts and images. Which flavour to take depends on what rights you want to keep for yourself. CC-0 - the same as public domain in the US, everybody can do what they want with the text. CC-BY - everybody can do what they want with the text as long they mention the license and your name. I am so full of myself to use that one. ;-) Then there are the more restrictive licenses with Share Alike, No Derivates and No Commercial use. http://creativecommons.org/choose/ has a questionaire for making that decision. CC-BY-SA is about the same as GPL, I think. I used that for some time but dropped the SA. Rolf http://meetthegimp.org ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Documentation on color spaces
Hi Elle, I hope you agree that I added a link to your documentation in our developer wiki: http://wiki.gimp.org/index.php/Users:Beginner_Developer%27s_FAQ Kind regards, Sven ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Documentation on color spaces
On Wed, Oct 9, 2013 at 10:32 PM, Elle Stone l.elle.st...@gmail.com wrote: On 10/9/13, Rolf Steinort i...@meetthegimp.org wrote: On 09.10.2013 15:20, Elle Stone wrote: If my Guide seems useful to developers, I'll put the content under an applicable license so it can be hosted elsewhere and modified by other people. Please do that! I'll make a video from it (well, parts of it, as usual with the books also ;-) ) I'm sure adding documentation is like adding code - it doesn't happen automagically. But if anyone wants to put (all or portions) of the Guide somewhere in Gimp documentation, I can supply a PDF or a latex file, or plain text, or whatever is convenient. And if having the Guide also on my website presents a conflict of some sort (I don't know how these things are supposed to work), I can remove the Guide from my website altogether. You are a skilled writer; you've got some home turf advantage though. Combined with your color knowledge you are be much more well suited to clarify what the babl format strings we keep using in GIMP mean, as well as how it fits into our overall scheme of things in current and future GIMP. What you do not understand; we might not quite understand ourselves yet either. The babl README/website, our lowest level of developer documentation relevant to this hasn't seen much improvement during the last half decade or so. This is generated from some static html in the docs directory of the source code in git. One could almost start with a link to your current write-up. I see no problem in the content our alternate versions of the content being used different places. I haven't considered the license of the documentation of babl/gegl separately from the project code itself before. But do not see a problem with including self-contained bits/chapters under a create-commons license; or some other compatible license on their websites. Øyvind -- ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Translator available
Hi, On Thu, Oct 10, 2013 at 4:35 AM, Abraham Mireles Alvarez abraham_al...@hotmail.com wrote: Hello everyone Just eanted to let you know that I am available as a translator in case you need help I'm not a translator for GIMP, who would know better what procedure there is. But I guess a first step would be to clone the git development repository of GIMP, compile it, and see what is missing or wrong. Maybe there could be an easier procedure for translators, where you could use existing builds, and just compile the po files, but I have no idea if such a process is in place. Because if you work off a released version, you can't be sure if something has not already been translated by someone else. Then you could edit the po files. Do you know about gettext syntax? This might be the next step. :-) If someone more versed into translation than me would answer you, that would be great, though. But I would suggest you to come on the IRC channel. Most of the contributors prefer to discuss through this channel, rather than email: http://www.gimp.org/irc.html Have fun! Jehan Spanish- english I got a 630 at the TOEFL :) Enviado desde mi iPhone ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/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
Re: [Gimp-developer] Documentation on color spaces
On Thu, Oct 10, 2013 at 3:58 AM, Jorge Tijerina wrote: Reading through this thread, could this mean that we can see CMYK in GIMP soon? (natively) It's unrelated :) Alexandre ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
