Re: [Gimp-user] Documenting Gimp Color Management
On Sat, 2008-02-09 at 03:06 +0100, Axel Wernicke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I just wanted to let you know that there is already something about the new color management features in the documentation. Feel free to read this - - http://docs.gimp.org/en/gimp-imaging-color-management.html - - http://docs.gimp.org/en/gimp-pimping.html#gimp-prefs-color-management - - http://docs.gimp.org/en/glossary.html#glossary-rendering-intent - - http://docs.gimp.org/en/gimp-imaging-color-management.html and please, don't hesitate to correct what's written or fill the gaps. Everything in there is to my best knowledge but I'm sure it is neither completely correct nor are all necessary topics in there yet. Greetings, lexA I am attaching a second installment of comments as a text file below. I'm afraid the comments come across just as criticisms, so let me emphasize how much I appreciate what you've already done. Ideally, rather than just complaining about this or that, I should suggest how I would phrase it instead. Unfortunately, I don't feel comfortable about writing documentation of this kind yet, so I would rather just raise points and hope you can figure out what I'm saying and include it in the documentation if it seems appropriate. I'm sure you will do a better job of it than I would at this stage. When I feel more comfortable, I will suggest appropriate wording. Also, remember that there are several color management issues and, more important, issues about exactly what gimp does that I find mysterious. So some of my comments might just indicate ignorance or misunderstanding. Even so, I am a relatively experienced gimp user who is Linux savvy and knows something about color management. So if I am confused by something, there is good chance that an average user will also be confused. I would find it easier to understand what gimp is actually doing if I could get at its guts. Instead, I have to do experiments and the results can sometimes be misleading. I've tried several times to look at code, but I've been defeated each time, not by the code, but by the complex structure of the source tree. Any suggestions about how to learn about that without making it my life's work would be appreciated. P.S: as Julien already mentioned - if you feel not comfortable writing docbook xml, just give us plain text to incorporate. - -- Remember: There are only two tools in life. WD-40, for when something doesn't move, and should, and Duct Tape, for when something is moving and it shouldn't. So does the universe explode if you spray duct tape with WD-40? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iD8DBQFHrQqeR9mXLVsAbiQRAntfAJ9FdQqHCMANjDzybGlMrY0tCMq9FACgsXAx AW7MEb5dkf7chKksvIUTc5o= =zTgP -END PGP SIGNATURE- ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user Gimp color management documentation. Here are some suggestions about the current color management documentation. The general import is that one must be very careful about what you say about what types of profiles may be present and about how they are used. There are many possible variations, and, as best I can tell from experimentation, there is little consistency. 1. In 1.2. Color Managed Workflow, under Input you say : 'Most digital cameras embed a color profile to individual photo files without user interaction.' My Nikon D80 most certainly doesn't embed any profile in normal use. A good guess would be that it has sRGB as a default profile, but I don't know. If I shoot raw using the nef format, then with ufraw I can specify input and output color profiles. I haven't myself figured out exactly what ufraw does with these profiles. I presume it uses the input profile somehow in converting from the raw data to RGB values. It could do different things with respect to the output profile. It could change the RGB values according to the profile and write those out without embedding the profile in the file. Or it could not change the RGB values but embed the profile in the output file. From some experimentation, my guess is the former. I couldn't find any profile in a ufraw output file. (I use iccdump.) I don't argue that what you say may not be true for some digital cameras, but I think it is a stretch to say that most digital cameras do that. 2. You also say 'Digital scanners usually come with a color profile, which they also attach to the scanned images.' I don't know about most digital scanners. I only know what happens with my Epson 3200 which I have used under Linux both with xsane and vuescan. These are the only choices for scanning software that I know of that are available under Linux. Of course, under Windows XP or MacOS, the vendor supplied software may be used in addition to some
Re: [Gimp-user] Documenting Gimp Color Management
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Leonard, Am 09.02.2008 um 17:58 schrieb Leonard Evens: On Sat, 2008-02-09 at 03:06 +0100, Axel Wernicke wrote: ... and please, don't hesitate to correct what's written or fill the gaps. Everything in there is to my best knowledge but I'm sure it is neither completely correct nor are all necessary topics in there yet. I am attaching a second installment of comments as a text file below. I'm afraid the comments come across just as criticisms, so let me emphasize how much I appreciate what you've already done. Ideally, Since I explicitly asked for it, I should (and do) stand that now ;) By now I did not fully examine what you wrote, but I'll do so in the next couple of days. rather than just complaining about this or that, I should suggest how I would phrase it instead. Unfortunately, I don't feel comfortable about writing documentation of this kind yet, so I would rather just raise points and hope you can figure out what I'm saying and include it in the documentation if it seems appropriate. I'm sure you will do a better job of it than I would at this stage. When I feel more comfortable, I will suggest appropriate wording. Well, let it put me this way: your english can't be worse than mine. Unfortunately there are right now 0 (in words: zero) native speaking people in the documentation team - the only reason for me writing english content is that there is no alternative :( ... I would find it easier to understand what gimp is actually doing if I could get at its guts. Instead, I have to do experiments and the results can sometimes be misleading. I've tried several times to look at code, but I've been defeated each time, not by the code, but by the complex structure of the source tree. Any suggestions about how to learn about that without making it my life's work would be appreciated. I most probably can't answer them too. If in doubt we need to ask the devs. Greetings, lexA - --- Remember: There are only two tools in life. WD-40, for when something doesn't move, and should, and Duct Tape, for when something is moving and it shouldn't. So does the universe explode if you spray duct tape with WD-40? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iD8DBQFHrjMcR9mXLVsAbiQRAlj2AJ0WqEC/8XM81gW5SMs4GZaMjpN+zACg9WZF JztRPAqgxQNeHWt7xVA1H1Y= =1fXZ -END PGP SIGNATURE- ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Documenting Gimp Color Management
On Sun, 2008-02-10 at 00:11 +0100, Axel Wernicke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Leonard, Am 09.02.2008 um 17:58 schrieb Leonard Evens: On Sat, 2008-02-09 at 03:06 +0100, Axel Wernicke wrote: ... and please, don't hesitate to correct what's written or fill the gaps. Everything in there is to my best knowledge but I'm sure it is neither completely correct nor are all necessary topics in there yet. I am attaching a second installment of comments as a text file below. I'm afraid the comments come across just as criticisms, so let me emphasize how much I appreciate what you've already done. Ideally, Since I explicitly asked for it, I should (and do) stand that now ;) By now I did not fully examine what you wrote, but I'll do so in the next couple of days. rather than just complaining about this or that, I should suggest how I would phrase it instead. Unfortunately, I don't feel comfortable about writing documentation of this kind yet, so I would rather just raise points and hope you can figure out what I'm saying and include it in the documentation if it seems appropriate. I'm sure you will do a better job of it than I would at this stage. When I feel more comfortable, I will suggest appropriate wording. Well, let it put me this way: your english can't be worse than mine. Unfortunately there are right now 0 (in words: zero) native speaking people in the documentation team - the only reason for me writing english content is that there is no alternative :( Your English is fine. My concerns about my writing documentation are more basic than that. I'm worried that were I to write documentation, I might make it so complicated it would be useless. It is question of deciding how to put things so people can understand it easily but aren't led astray by having things be oversimplified. But give me some time. I've lots of experience explaining complex matters to generations of mathematics students, and some of that may carry over. I would be happy to be the resident native speaker of English. I haven't seen any problems of that nature yet, but should I find any, I will be happy to correct them. ... I would find it easier to understand what gimp is actually doing if I could get at its guts. Instead, I have to do experiments and the results can sometimes be misleading. I've tried several times to look at code, but I've been defeated each time, not by the code, but by the complex structure of the source tree. Any suggestions about how to learn about that without making it my life's work would be appreciated. I most probably can't answer them too. If in doubt we need to ask the devs. Greetings, lexA - --- Remember: There are only two tools in life. WD-40, for when something doesn't move, and should, and Duct Tape, for when something is moving and it shouldn't. So does the universe explode if you spray duct tape with WD-40? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iD8DBQFHrjMcR9mXLVsAbiQRAlj2AJ0WqEC/8XM81gW5SMs4GZaMjpN+zACg9WZF JztRPAqgxQNeHWt7xVA1H1Y= =1fXZ -END PGP SIGNATURE- ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] random plugin loading problem
Hi,
I wrote a plugin few days back
(GimpPublishrhttp://code.google.com/p/altcanvas/wiki/GimpPublishr)
to publish images to Flickr/Picasa. It was tried by many and I had received
various complaints about plugin not getting loaded, even after deploying in
right directory. In some cases they had hit a bug in plugin which would
prevent Gimp from loading the plugin. In recent versions I fixed some bugs
in the plugin and put a top level try-except block with a crash report
dialog, so that any bug in plugin won't go unnoticed silently.
But even after that I kept hearing few cases where users won't see the
plugin loaded and still won't get any crash report.
Today I started working on the same plugin again after some gap. Today I
tried it under two different installations of Gimp - on my Fedora 8 desktop
and in a Ubuntu VM. I am running same version of Gimp at both places, using
same plugin files. Interestingly, the plugin doesn't load in my ubuntu VM,
but it does in my Fedora 8 desktop. I cleaned my $HOME/.gimp-2.4 directory
multiple times, but same result.
Note these observations:
1) I also noticed that when the plugin gets loaded successfully on my fedora
box, the $HOME/.gimp-2.4/pluginrc file gets modified and I see following
entry appended to it:
(plug-in-def /home/jayesh/.gimp-2.4/plug-ins/publishr.py 1202602069
I don't see that happening on Ubuntu VM.
2) On BOTH the systems, when the Gimp splash image is diplaying the plugins
it is loading at startup, I DO SEE publishr.py (my plugin file) being
loaded. But I doubt that the register() function gets called in the ubuntu
case. I put a deliberate raise Exception just before register() function,
however it doesn't make any difference.
Both are running same gimp version.
$ gimp --version
GNU Image Manipulation Program version 2.4.0-rc3
The dump of gimprc is same on both systems (except for the web-browser
parameter). For Fedora 8 it is as follows.
$ gimp --dump-gimprc
# Dump of the GIMP default configuration
(temp-path ${gimp_dir}/tmp)
(swap-path ${gimp_dir})
(num-processors 1)
(tile-cache-size 1024M)
(interpolation-type cubic)
(plug-in-path ${gimp_dir}/plug-ins:${gimp_plug_in_dir}/plug-ins)
(module-path ${gimp_dir}/modules:${gimp_plug_in_dir}/modules)
(interpreter-path
${gimp_dir}/interpreters:${gimp_plug_in_dir}/interpreters)
(environ-path ${gimp_dir}/environ:${gimp_plug_in_dir}/environ)
(brush-path ${gimp_dir}/brushes:${gimp_data_dir}/brushes)
(brush-path-writable ${gimp_dir}/brushes)
(pattern-path ${gimp_dir}/patterns:${gimp_data_dir}/patterns)
(pattern-path-writable ${gimp_dir}/patterns)
(palette-path ${gimp_dir}/palettes:${gimp_data_dir}/palettes)
(palette-path-writable ${gimp_dir}/palettes)
(gradient-path ${gimp_dir}/gradients:${gimp_data_dir}/gradients)
(gradient-path-writable ${gimp_dir}/gradients)
(font-path ${gimp_dir}/fonts:${gimp_data_dir}/fonts)
(default-brush Circle (11))
(default-pattern Pine)
(default-palette Default)
(default-gradient FG to BG (RGB))
(default-font Sans)
(global-brush yes)
(global-pattern yes)
(global-palette yes)
(global-gradient yes)
(global-font yes)
(default-image
(width 420)
(height 300)
(unit pixels)
(xresolution 72.00)
(yresolution 72.00)
(resolution-unit inches)
(image-type rgb)
(fill-type background-fill)
(comment Created with GIMP))
(default-grid
(style intersections)
(fgcolor (color-rgba 0.00 0.00 0.00 1.00))
(bgcolor (color-rgba 1.00 1.00 1.00 1.00))
(xspacing 32.00)
(yspacing 32.00)
(spacing-unit inches)
(xoffset 0.00)
(yoffset 0.00)
(offset-unit inches))
(undo-levels 5)
(undo-size 64M)
(undo-preview-size large)
(plug-in-history-size 10)
(pluginrc-path ${gimp_dir}/pluginrc)
(layer-previews yes)
(layer-preview-size medium)
(thumbnail-size normal)
(thumbnail-filesize-limit 4M)
(install-colormap no)
(min-colors 144)
(color-management
(mode display)
(display-profile-from-gdk yes)
(display-rendering-intent perceptual)
(simulation-rendering-intent perceptual)
(display-module CdisplayLcms))
(color-profile-policy ask)
(save-document-history yes)
(transparency-size medium-checks)
(transparency-type gray-checks)
(snap-distance 8)
(marching-ants-speed 100)
(resize-windows-on-zoom no)
(resize-windows-on-resize no)
(default-dot-for-dot yes)
(initial-zoom-to-fit yes)
(perfect-mouse yes)
(cursor-mode tool-icon)
(cursor-updating yes)
(show-brush-outline yes)
(show-paint-tool-cursor yes)
(image-title-format %D*%f-%p.%i (%t, %L) %wx%h)
(image-status-format %n (%m))
(confirm-on-close yes)
(monitor-xresolution 96.00)
(monitor-yresolution 96.00)
(monitor-resolution-from-windowing-system yes)
(navigation-preview-size medium)
(default-view
(show-menubar yes)
(show-rulers yes)
(show-scrollbars yes)
(show-statusbar yes)
(show-selection yes)
(show-layer-boundary yes)
(show-guides yes)
(show-grid no)
(show-sample-points yes)
(padding-mode
[Gimp-user] digital camera photo settings
Does anyone know if JPEG stores the settings from a digital camera and
how to read them?
ie: ISO setting, etc.?
I like to experiment with settings, would be nice not to have to write
each one down.
--
Anthony Ettinger
408-656-2473
http://anthony.ettinger.name
@pets = Pets.find_all_by_species('dog')
@pets.each do |dog| {
if dog.name == 'Farley'
dog.nick = 'Sir Barks-A-lot'
elsif dog.name == 'Bonita'
dog.nick = 'Princess Boo'
else
dog.nick = 'Doggie?'
end
}
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] digital camera photo settings
Does anyone know if JPEG stores the settings from a digital camera and how to read them? ie: ISO setting, etc.? I like to experiment with settings, would be nice not to have to write each one down. Perhaps you want the exif data Make sure you have the exif libraries install, and at the prompt, type # exif blah.jpeg Owen ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] digital camera photo settings
On Sun, 2008-02-10 at 14:04 +1100, Owen wrote: Perhaps you want the exif data Make sure you have the exif libraries install, and at the prompt, type # exif blah.jpeg I was wondering - doesn't GIMP 2.4 support EXIF data now? I had a JPEG with some EXIF data in it that I could read with GQView but I couldn't find a way to read the data in GIMP. Is there one? -- Michael J. Hammel Ximba End User Software [EMAIL PROTECTED] http://www.ximba.org LFS UserID: 16857 -- Vision is the ability to see potential in the work of others. Robert X. Cringley, Accidental Empires ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
