gThumb IPTC metadata problem might be fixed in version 2.11.90

After filing a bug on the IPTC metadata issue in gThumb 2.11, namely that the application doesn't put the data entered in the "comment" area into the right format for IPTC, I heard from one of the developers that my bug was similar to another bug that was fixed in version 2.11.90, and he suggested I try that version.

My Fedora 13 skills are rudimentary, and I haven't yet been able to build gThumb 2.11.90 from source, and I haven't yet had the time to grab the required dependencies to install the RPM for Fedora 14 (and I do have that RPM). I'll get around to it, I'm sure.

What I'd like to do is thank the gThumb team for being so responsive. The developers did a lot of overhauling to gThumb between 2.10 and 2.11, and I can understand there being a few glitches. I'm just glad the process seems to be working, and I hope that gThumb will be back in my workflow very soon.

All I really need to make gThumb the ultimate photo-editing app for my purposes is the ability to sharpen images in the app. As it is, gThumb allows me to edit an image with another program, say the GIMP, and then return to gThumb. If I do this just right, gThumb returns the IPTC metadata to my JPG image file after the GIMP zaps it out. A GIMP that also recognized, edited and didn't obliterate IPTC data would solve many a problem. I've brought this up before maybe a dozen times, and I'm not expecting anything to happen regarding the GIMP and IPTC. I continue to be thankful that gThumb and digiKam handle IPTC.

I've tried Mapivi, which does handle IPTC data, but it didn't work particularly well for me.
Fotoxx also didn't work well for me, but I'm open to trying both of these applications again. I'd also love to see IPTC capability in Krita; that alone would push me into KDE (a desktop environment that I tried recently in Fedora 13 but didn't much like).

I'll close by saying that gThumb remains my No. 1 image editor.