Bug 701624

Summary: file names with spaces don't work
Product: [Fedora] Fedora Reporter: Dj YB <yehielb>
Component: pdftkAssignee: Jochen Schmitt <jochen>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: jochen, oget.fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-05 17:41:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dj YB 2011-05-03 12:00:28 UTC 
Description of problem:
when using the service menu operations on files with spaces in their path (the file name or the path to it) nothing happens.

Version-Release number of selected component (if applicable):
1.41

How reproducible:
always

Steps to Reproduce:
1.try to do something with file with spaces in it's name
2.
3.
  
Actual results:
nothing

Expected results:
the requested operation

Additional info:
Thanks.
Comment 1 Orcan Ogetbil 2011-05-05 02:38:07 UTC 
This seems to be fixed in 1.44, which is only available for Fedora 15 and above for the time being.

Jochen, what shall we do?
Comment 2 Jochen Schmitt 2011-05-05 17:41:05 UTC 
In the Changelog.txt file of pdftk-1.44 I have found the following sentence:

Introduced update_info_utf8, dump_data_utf8 and
dump_data_fields_utf8 to provide UTF-8 companions to update_info,
dump_data and dump_data_fields. These latter operations use XML
numerical entities to encode non-ASCII characters. In version 1.43,
we changed the encoding for update_info to UTF-8, but that made it
incompatible with dump_data and also broke some downstream
applications. By introducing these UTF-8 operations, we can revert
update_info to its original behavior.

Because an update may violate our new update policy, I must close this bug with 'Fixed for next release'