GNOME Bugzilla – Bug 659509
opening file with special characters fails
Last modified: 2012-12-20 05:20:37 UTC
When I open a .psd file by double clicking the icon from windows, it is associated to gimp so gimp tries to open it, if the file name has special characters in this case a special kind of e used in Ukrainian, I get the error that the photoshop plugin can not open the file. But if I drag the file into an open gimp window it opens fine in that case. Or if i rename the special e to a normal e it opens fine by double clicking from windows.
What version of GIMP are you using? Which operating system are you on? What is the name of the file which has the problem?
version 2.6.11 windows server 2008 r2 64 bit między mapami.psd
ender says (on IRC) this could be due to something similar to bug #522131.
I guess it is not a photoshop plugin issue but a general gimp issue, I created a new xcf and saved it as między mapami, double clicked it in windows and gimp gave the error : Opening 'C:\Users\XXX\Pictures\miedzy mapami.xcf' failed: Could not open 'C:\Users\XXX\Pictures\miedzy mapami.xcf' for reading: No such file or directory Notice in the error message the ę was changed to e. So it probably is an issue with the command line argument as in bug 522131.
Please try GIMP 2.7.4 and report back, we won't fix 2.6 bugs any longer.
Could you please try to reproduce problem with GIMP 2.7.4 or later version and update the bug report with your findings, tia.
I can confirm this problem with GIMP 2.7.4 (Windows 7) and a file called "między mapami.xcf". btw. The title of the bug-report should be changed.
I thought that was fixed for good :( Can one of the windows guys please look into this?
*** Bug 677637 has been marked as a duplicate of this bug. ***
*** Bug 678443 has been marked as a duplicate of this bug. ***
FYI: Non-standard characters in file names seem to be a more general problem. See also bug #683081.
*** Bug 683081 has been marked as a duplicate of this bug. ***
*** Bug 690537 has been marked as a duplicate of this bug. ***
I see the often-proposed duplication of bug #522131, too. *** This bug has been marked as a duplicate of bug 522131 ***