On Wednesday 15 November 2006 18:50, gimp-developer-request@xxxxxxxxxxxxxxxxxxxxxx wrote: > Send Gimp-developer mailing list submissions to > gimp-developer@xxxxxxxxxxxxxxxxxxxxxx > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer > or, via email, send a message with subject or body 'help' to > gimp-developer-request@xxxxxxxxxxxxxxxxxxxxxx > > You can reach the person managing the list at > gimp-developer-owner@xxxxxxxxxxxxxxxxxxxxxx > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Gimp-developer digest..." > > > Today's Topics: > > 1. GIMP 2 book, your opinion is...? (Leon Brooks) > 2. 2.4 showstoppers (Sven Neumann) > 3. Re: 2.4 showstoppers (Alexandre Prokoudine) > 4. Re: 2.4 showstoppers (Sven Neumann) > 5. gimprc confusion (gg@xxxxxxxxxxx) > 6. Re: gimprc confusion (gg@xxxxxxxxxxx) > 7. Re: gimprc confusion (Michael Schumacher) > 8. Re: gimprc confusion (Sven Neumann) > > > ------------------------------------------------------------------- >--- > > Message: 1 > Date: Wed, 15 Nov 2006 14:40:09 +0800 > From: Leon Brooks <leon-gimp@xxxxxxxxxxxxxxxxxxx> > Subject: GIMP 2 book, your opinion is...? > To: gimp-developer@xxxxxxxxxxxxxxxxxxxxxx, > gimp-user@xxxxxxxxxxxxxxxxxxxxxx > Message-ID: <200611151440.09541.leon-gimp@xxxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > Has anyone read /GIMP 2 for Photographers/ yet? > > There's a review up at: > > http://www.desktoplinux.com/news/NS5105451578.html > > I'd value your opinion, if you've formed one. Particularly if > you're a photographer of any sort. > > Cheers; Leon > > > ------------------------------ > > Message: 2 > Date: Wed, 15 Nov 2006 09:40:46 +0100 > From: Sven Neumann <sven@xxxxxxxx> > Subject: 2.4 showstoppers > To: gimp-developer@xxxxxxxxxxxxxxxxxxxxxx > Message-ID: <1163580046.27235.30.camel@bender> > Content-Type: text/plain > > Moin, > > slowly but steadily the state of GIMP 2.3 is reaching a point where > it can be released as 2.4. I would like to point out some > showstoppers in the hope that we can get some help with them. There > is also the list of bugs on the 2.4 milestone in Bugzilla and this > mail somewhat overlaps with that. But it also mentions a few things > that are not in Bugzilla (but probably should be). > > Here's a small list of outstanding items for GIMP 2.4, from the top > of my head, incomplete and subject to discussion: > > > Finish rectangle tools > > The rewritten rectangle tools (rect and ellipse select as well as > crop) are getting better, but there are still some regressions > (mainly in the Crop tool, see Bugzilla) and the tool options still > need an overhaul. Would be nice if we could come up with a decent > tool options UI proposal, then implement it. > > > Finish color management > > Main feature missing here is giving the display filters access to > the image's color profile. As soon as that is implemented, we > should have a prepress professional review the functionality. I > would also like to further improve the color management > preferences. In this case it seems like a good idea to try to get > something that resembles the Photoshop color management > configuration in terms of terminology and policies. > <snipped> > > Sven I have been playing with the color management in CVS and it is getting there for sure. My thinking is the choice of controls and terminology should be guided by the 3 modes you have. 1. No color management means that and everything assumes RGB with no display compensation. 2. Managed Display - To me mode this should be used for web graphics and users with the large majority of inkjets which are indeed RGB devices in that they expect RGB data. 3. Press Simulation - Exactly that. Simulating CMYK Printers of all kinds. In the case of #3, you could argue that having a choice to enable some form of gamut warning. Mind you gamut warnings are just that. I would not enable this for # 2 One thing which needs fixing is profile locations. Finding and setting the profiles is not obvious on Linux On Linux/*nix, we've outlined those directories on openicc and most of it is taking hold as a spec. This should be a recursive search as some profile packages are now available for distros and they sometimes separate RGB and CMYK locations. Windows NT and Win9x have different default locations, but they should be searched automatically IMO. The trickier bit for me is how you handle importing CMYK images. I just did a test and it detects there is an embedded icc profile and asks correctly if I want to replace it or keep it. However, it is CMYK, yet asks to replace sRGB with a differently named SRGB profile and the console outputs: '** (lcms:16300): WARNING **: Attached color profile is not for RGB color space.' My thinking is that any CMYK image imported should have a simple warning that it is not currently supported and a best effort conversion is made to RGB. File > Properties might be good place also to note if a given image has an embedded profile. I'm game to writeup some docs before 2.4 is done on a color management. section. Without good docs, this will flood the mail lists and IRC with questions. I did not mean this to be a comprehensive review and I know this is still a work in progress, but it is great to see what has been done so far. Peter
Attachment:
pgpyPgQru8FAQ.pgp
Description: PGP signature
_______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
