Problem editing the current image in an external editor

Good morning,

I needed to use the export function of the edited image in order to open it in GIMP. It did not work. In the preferences, I gave the right path to the GIMP installation folder (bin). As output folder, I selected “same as input image”. By clicking on the icon image, nothing happens and GIMP has not been launched.

I tried to export via the third option, using the personal command line, and specifying the absolute path to the GIMP executable. At my house :

D:\Program Files\GIMP 2\bin\gimp-2.10.exe

By clicking on the icon ![image|42x44(upload://foOAuGtUYv5ERTKZHNeH6PKDtBs.png), this time GIMP launches but an error message appears:

image

You will notice that the edited image path contains accented characters. Apparently, these accented characters are misinterpreted by GIMP, due to a bad character set.

It’s very annoying. I believe this is a bug to fix in RawTherapee. It should convert the path string to the character set compatible with GIMP.

I specify that I work under Windows 11, and it is possible that this problem of accented characters does not occur under other operating systems.

Can anyone help me? Where do I send the report of this malfunction so that the designers of RawTherapee can correct this problem?

Thank you for your attention and your answers. Good day !

Hello, make a folder on your desktop named Multimedia - so without an accent aigu -, place a photo in it, then navigate within RawTherapee to that folder, open the photo and send it to Gimp. Does that work?

I don’t know if the fault comes from RT or from Gimp, but you can file an issue at the following link. Perhaps an existing issue describes the same problem, so have a look first.

Maybe the same problem ART had too.

Hello, and thank you for your response.

I tried to do what you advise me. I created a folder named “Multimedia” (no accent) on my desktop. I placed in it an already developed dng image, with a name without spaces or accented characters. See the screenshot:

I opened that folder in RT, opened the image in the editor, clicked on the export button, and that doesn’t work either.

I think that try is no good either, because the actual path to the image is:

“C:\Users\Thierry Preusser\Desktop\Multimedia”,

and there is a space in my username. Therefore, wanting to send this image to GIMP, it does not work either and GIMP does not launch.

I tried again with another try, this time placing my image in a “D:\Multimedia” folder. This path does not contain spaces or accented characters. I opened this folder in RT, opened the image in the editor, clicked the export button, and it still doesn’t work! In this test, the first option in the export window was selected:

So, out of conscience, I checked the third option of the export window, by introducing the absolute path to the GIMP executable, as a personal command line:

This time bingo! RT exported the image in tiff format, GIMP launched to import the image, not without first displaying a window concerning the conversion of the color profile:

image

I found my image opened in GIMP, with the rendering of the development done in RawTherapee. This is the correct operation.

So I’m going to open a bug ticket on the site you gave me the link.

Thanks for the help, we’re moving forward.

Beautiful day.

@preuthier
THE GIMP installation folder is not “bin”. It should be “GIMP 2”.

Dogged does it ! Votre ténacité est récompensée. :wink:

You can get rid of that question. In Gimp go to Preferences, Importing/Exporting images - Color profile policy. Change ‘Ask what to do’ in Keep or Convert.

En Français: Préférences, Importation et exportation d’images, Politique de profil de couleur, changez ‘Demander ce qu’il faut faire’ vers Conserver ou Convertir.

Bonne journée à vous.

Yes, that would be more convenient, but I still want to see this color profile conversion step. It lets me know what I’m doing.

Thank you so much ! That works. This is a mystery solved. Only this problem of accented characters remains, and for that I will report the problem on Github.