On Thu, Sep 08, 2005 at 07:43:52PM +0200, Stephan Brunner wrote:

Hi all,

I'm writing my first gimp-perl plug-in and it is really doing what it's supposed to do - except one thing:
After some modifications of an image, the script saves the image with gimp_jpeg_save, but there is no "write exif"-option and so no exif-info is written with the saved jpg. In the normal GUI "File->Save"-Dialog, however, there is this option and it works as expected.

Did I miss something, or is there really no way to get the same exif-containing jpg by script than by interactive mode?

can you use perl directly to use libexif?

as far as i know, the gimps metadata editor is not committed yet even in cvs if it exists. the developers have many complaints about how it works as well. i think it should be easier and quicker just to use perl to do it while they sort through things and become inspired to commit whatever things they have done so far.

at least, this was the approach i was going to take with python and my scripting attempts ....

carol

On 9/8/05, Stephan Brunner wrote:

After some modifications of an image, the script saves the image with gimp_jpeg_save, but there is no "write exif"-option and so no exif-info is written with the saved jpg. In the normal GUI "File->Save"-Dialog, however, there is this option and it works as expected.

This is probably a limitation in gimp-jpeg-save -- try looking in the procedure browser to see if there is an alternative function to do what you want. If not, gimp-perl has been known to be slightly outdated and/or semi-broken for a while, and it may be easier to write scripts in python or script-fu (although I love perl myself -- I'd use it if I could, but I find that it's support is sketchy to date, unfortunately).

As for using 2.2.6 on Sarge -- isn't a 2.2.7cvs-something that "reads" 2.2.8 package available in Debian? Because that's what I'm using...