import fails on german umlauts in path or file name

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use any german Umlaut (ä, ö, ü) in a folder or file Name
2. Import Photos from that folder / with that name

What is the expected output? What do you see instead?
Should Import, but gives me this:

Traceback (most recent call last):
   File "./jbrout.py", line 1521, in on_menu_refresh
    self.on_drop_folders_from_os(model,[path])
   File "./jbrout.py", line 1616, in on_drop_folders_from_os
    for nb in iterator:
   File "/home/lomex/filme/jbrout/jbrout/db.py", line 132, in add
    self.__addPhoto( file ,tags,filesInBasket)
   File "/home/lomex/filme/jbrout/jbrout/db.py", line 192, in __addPhoto
    raise Exception(err+"\nPhoto has incorrect exif/iptc tags, can't be imported 
:\n"+str([file,]))
 Exception: Traceback (most recent call last):
  File "/home/lomex/filme/jbrout/jbrout/db.py", line 181, in __addPhoto
    needAutoRotation=DBPhotos.autorotAtImport,
  File "/home/lomex/jb/jbrout/jbrout/tools.py", line 195, in __init__
    self.__info = pyexiv2.Image(self.__file)
  File "/usr/lib/pymodules/python2.5/pyexiv2.py", line 396, in __init__
    libpyexiv2.Image.__init__(self, filename)
IOError: /home/lomex/filme/gi-joe-räise-of-cobra.jpg: Failed to open the data 
source: Datei 
oder Verzeichnis nicht gefunden (errno = 2)

Photo has incorrect exif/iptc tags, can't be imported :
[u'/home/lomex/filme/gi-joe-r\xe4ise-of-cobra.jpg']

What version of the product are you using? On what operating system?
rev 269 from svn - debian GNU/linux

Original issue reported on code.google.com by lome...@googlemail.com on 13 Oct 2009 at 4:05

[GoogleCodeExporter]

I can not reproduce this error.  

What versions of pyexiv2 and exiv2 are you running and does it make any 
difference if 
you use the add folder button instead of dragging and dropping or what 
application you 
drag and drop from.  

Original comment by r...@wallace.gen.nz on 16 Dec 2009 at 2:52

[GoogleCodeExporter]

still happens with rev278 from google svn

traceback seems almost same:

Traceback (most recent call last):
  File "./jbrout.py", line 2542, in on_btn_addFolder_clicked
    self.on_drop_folders_from_os(self.treeviewdb.get_model(),[folder])
  File "./jbrout.py", line 1626, in on_drop_folders_from_os
    for nb in iterator:
  File "/home/lomex/jbrout-read-only/jbrout/jbrout/db.py", line 132, in add
    self.__addPhoto( file ,tags,filesInBasket)
  File "/home/lomex/jbrout-read-only/jbrout/jbrout/db.py", line 192, in __addPhoto
    raise Exception(err+"\nPhoto has incorrect exif/iptc tags, can't be imported :\n"+str([file,]))
Exception: Traceback (most recent call last):
  File "/home/lomex/jbrout-read-only/jbrout/jbrout/db.py", line 181, in __addPhoto
    needAutoRotation=DBPhotos.autorotAtImport,
  File "/home/lomex/jbrout-read-only/jbrout/jbrout/tools.py", line 195, in __init__
    self.__info = pyexiv2.Image(self.__file)
  File "/usr/lib/pymodules/python2.5/pyexiv2.py", line 396, in __init__
    libpyexiv2.Image.__init__(self, filename)
IOError: /home/lomex/test/hübsch.jpg: Failed to open the data source: Datei 
oder Verzeichnis nicht 
gefunden (errno = 2)

Photo has incorrect exif/iptc tags, can't be imported :
[u'/home/lomex/test/h\xfcbsch.jpg']

(in the traceback on my console in the line starting with "IOError", the 
"umlaut" (is there an english 
word for that?) was printed fine, after pasting it here it was two unreadable 
characters dont know what it 
will be after klicking save changes)

dont know how to get the version of the libs, maybe this is helpful:
the debian package "python-pyexiv2" is version 0.1.3-4
the shared object of the c lib is called "libexiv2.so.5.3.1"

lol? never used dragndrop. i do only import photos by klicking the add folder 
button (any other way?)
on_drop_folders_from_os is also called after a folder was selected after having 
clicked the add folder 
buttin, right?

Original comment by lome...@googlemail.com on 16 Dec 2009 at 3:19

[GoogleCodeExporter]

can't reproduce that

don't hesitate to re-open if needed

Original comment by manat...@gmail.com on 11 Oct 2010 at 6:49

• Changed state: Invalid

[GoogleCodeExporter]

youre right, can't reproduce this any more. this issue is deprecated
seems like some changes in to tools.py make sure everything works fine with the 
codings

Original comment by lome...@googlemail.com on 11 Oct 2010 at 7:25