Bug 200888

Summary: GIMP doesn't handle spaces in files correctly.
Product: [Fedora] Fedora Reporter: Armijn Hemel <armijn>
Component: gimpAssignee: Nils Philippsen <nphilipp>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-15 15:10:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Armijn Hemel 2006-08-01 12:18:38 UTC 
Description of problem:

GIMP doesn't handle spaces in files correctly. When I open an image, that has
spaces in its filename and then resave it, GIMP will replace it with %20. The
file ends up with %20 in its filename on disk. So, before it is written to disk
the %20 is not translated to a space.

Version-Release number of selected component (if applicable):
gimp-2.2.12-1.fc5

How reproducible:

Always

Steps to Reproduce:
1. open an image, save it to a file with spaces in its name
2. reopen the image, save it again. All spaces in the name will be replaced by %20
  
Actual results:

filename changed, spaces were replaced by %20

Expected results:

I would have expected that the spaces would be left intact.

Additional info:
Comment 1 Armijn Hemel 2006-08-01 14:18:59 UTC 
It seems to be a known bug in GIMP: http://bugzilla.gnome.org/show_bug.cgi?id=347544
Comment 2 Nils Philippsen 2006-08-02 14:47:20 UTC 
gimp-2.2.12-3 which includes the upstream fix are building right now for Rawhide
and FC-5.
Comment 3 Fedora Update System 2006-08-04 17:47:15 UTC 
gimp-2.2.12-3.fc5 has been pushed for fc5, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.
Comment 4 Armijn Hemel 2006-08-15 15:10:59 UTC 
Everything works ok now, so I guess this report can be closed.