After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 165002 - script-fu-path ignored, contains non-ascii-character (german umlaut)
script-fu-path ignored, contains non-ascii-character (german umlaut)
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Script-Fu
2.2.x
Other Windows
: Low minor
: 2.2
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-01-23 17:31 UTC by Guenther Dirks
Modified: 2008-01-15 12:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Guenther Dirks 2005-01-23 17:31:20 UTC
Hello,

just a minor problem with my GIMP on Windows:

I like to seperate additionals plugins and scripts from those that are 
originally distributed with the GIMP package. So I am storing the additional 
plugins and scripts in

%USERPROFILE%\.gimp-2.2\plugins and
%USERPROFILE%\.gimp-2.2\scripts

This works fine for the plugins (and brushes, palettes, patterns, etc.), but 
not for the scripts. My first thought was that this is because of the non-
ascii character in my %USERPROFILE% ("C:\Dokumente und Einstellungen\Günther 
Dirks\"), but it's only the script path that's not working.

I checked File/Preferences/Directories/Scripts 
(Datei/Einstellungen/Ordner/Skripte in german). It contains my private script 
path.

I checked the gimprc file, too. It contains the line

(script-fu-path "C:\\Dokumente und Einstellungen\\Günther Dirks\\.gimp-2.2
\\scripts;C:\\Programme\\GIMP-2.2\\share\\gimp\\2.0\\scripts")

Neither changing "Günther" to "Günther" nor removing the entire line changes 
the problem.

A workaround is to adding another script folder in the preferences, that 
doesn't contain non-ascii character ("C:\foo").

Regards,

Günther (Guenther)
Comment 1 Guenther Dirks 2005-01-23 17:38:38 UTC
GTK+ 2 for Windows (version 2.4.14) and GIMP 2.2.0 were downloaded from 
http://gimp-win.sourceforge.net/

This problem existed already in GIMP 2.0.x (Windows).
Comment 2 Sven Neumann 2005-01-23 19:58:46 UTC
Sounds like the filename encoding problems that were recently addressed in glib.
You should try with glib-2.6.
Comment 3 Guenther Dirks 2005-01-23 20:27:38 UTC
Thanks. 
I will try it with glib-2.6. Unfortunately I'm unable to compile it myself. So 
I will wait, until someone has done it.

Do you have a guess why only the script path is affected and all the other 
paths work?
Comment 4 Guenther Dirks 2005-01-25 19:25:37 UTC
Hello,

just for the record:
I' ve just upgraded to GIMP 2.2.3, but stayed with GTK+ 2.4.14. 

As GTK+ remained the same, the problem still exists.

I will go on as Sven Neumann suggested.

Günther
Comment 5 weskaggs 2005-02-25 19:45:45 UTC
Setting as NEEDINFO because we need to know whether upgrading glib sovles the
problem.
Comment 6 Guenther Dirks 2005-02-25 19:50:19 UTC
Sorry for not having tested this with glib-2.6! I will do it tomorrow.

Günther
Comment 7 weskaggs 2005-02-26 01:21:36 UTC
Thanks.  Didn't mean to rush you, just doing some Bugzilla housekeeping.
Comment 8 Guenther Dirks 2005-02-27 09:40:05 UTC
Hello,

I tried GTK+ 2.6.2 together with GIMP 2.2.3 (all from http://gimp-
win.sourceforge.net/ and http://sourceforge.net/projects/gimp-win/) this 
morning. 

I'm not sure if this combination is supposed to work, because my initial 
problem is not solved, while a new encoding problem has occured.

Some details:
- Windows XP SP2, german encoding ("DE")
- %USERPROFILE% contains german umlaut ("C:\Dokumente und 
Einstellungen\Günther Dirks")
- Uninstalled GTK+ 2.4.14, but left GIMP 2.2.3 installed
- Installed GTK+ 2.6.2
- Removed GIMP settings (directories .gimp-2.2 and .thumbnails in my %
USERPROFILE%)

Unchanged behaviour:
- scripts in %USERPROFILE%/.gimp-2.2/scripts are not recognized
- plug-ins, patterns, etc in %USERPROFILE%/.gimp-2.2 work fine

New problem:
- Thumbnails can not be written. When I open an image with "Datei + Öffnen" 
(File + Open), GIMP tries to generate and save the thumbnail. Saving the 
thumbnail fails with:

GIMP Meldung

»C:\Dokumente und Einstellungen\G?nther Dirks\.thumbnails\normal\gimp-thumb-
1616-9b36a26e (invalid encoding)« konnte nicht zum Schreiben geöffnet werden: 
Invalid argument

In english probably:
GIMP Message

»C:\Dokumente und Einstellungen\G?nther Dirks\.thumbnails\normal\gimp-thumb-
1616-9b36a26e (invalid encoding)« could not be opened for saving: Invalid 
argument

Günther

Comment 9 Sven Neumann 2005-02-27 12:15:47 UTC
Your new problem is supposed to be fixed (or rather worked around) with GIMP 2.2.4.
Comment 10 weskaggs 2005-02-28 17:41:44 UTC
Thanks for the information; removing NEEDINFO flag.
Comment 11 Guenther Dirks 2005-03-04 15:40:47 UTC
Hello,

I've tried GIMP 2.2.4 and GTK+ 2.6.2 (all from http://gimp-
win.sourceforge.net/) today. 

Unfortunately, the encoding problems (including the new preview problem) 
remained.

All details like comment #8. 

Guenther
Comment 12 Sven Neumann 2005-03-04 16:14:30 UTC
Let's concentrate on the script-fu problem here. Changing the component to
Script-Fu since it seems pretty clear that the problem is there.
Comment 13 Sven Neumann 2005-03-04 16:31:07 UTC
Well, this could not have worked (on a filesystem with non-UTF-8 encoding).

2005-03-04  Sven Neumann  <sven@gimp.org>

	* plug-ins/script-fu/script-fu-scripts.c (script_fu_find_scripts):
	need to convert script-fu-path to filesystem encoding. Should fix
	bug #165002.
Comment 14 Guenther Dirks 2005-03-04 18:58:10 UTC
Thanks Sven, that was quick!

What about the preview problem with GTK+ 2.6.2?

Submit a new bug report?

Guenther
Comment 15 Sven Neumann 2005-03-04 19:06:43 UTC
Actually there already is one but that got reassigned to glib. See bug #167973.