Tam-Lin / comictagger

Automatically exported from code.google.com/p/comictagger
0 stars 0 forks source link

UnicodeEncodeError: 'ascii' codec can't encode character u'\xbd' in position 59: ordinal not in range(128) #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. comictagger.py -v -e --delete-rar Darkchylde\ Redemption\ 0\ ½\ --\ 
\[\]\[DC\].cbr

What is the expected output? What do you see instead?
Traceback (most recent call last):
  File "/usr/local/bin/comictagger.py", line 5, in <module>
    ctmain()
  File "/usr/local/lib/python2.7/dist-packages/comictaggerlib/main.py", line 54, in ctmain
    cli.cli_mode( opts, settings )
  File "/usr/local/lib/python2.7/dist-packages/comictaggerlib/cli.py", line 184, in cli_mode
    process_file_cli( f, opts, settings, match_results )
  File "/usr/local/lib/python2.7/dist-packages/comictaggerlib/cli.py", line 505, in process_file_cli
    if ca.exportAsZip( new_file ):
  File "/usr/local/lib/python2.7/dist-packages/comictaggerlib/comicarchive.py", line 1044, in exportAsZip
    return zip_archiver.copyFromArchive( self.archiver )
  File "/usr/local/lib/python2.7/dist-packages/comictaggerlib/comicarchive.py", line 225, in copyFromArchive
    print >> sys.stderr, "Error while copying to {0}: {1}".format(self.path, e)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xbd' in position 
59: ordinal not in range(128)

What version of the product are you using? On what operating system?
1.1.9, Ubuntu 12.10

Please provide any additional information below.
I suspect comictagger doesn't like the ½ (Unicode?) character in the filename.

Original issue reported on code.google.com by olin...@gmail.com on 5 Dec 2013 at 10:23

GoogleCodeExporter commented 9 years ago
I confirmed the ComicTagger GUI will pull the 1/2 Unicode character from 
ComicVine fine. For example look up the first issue of "Tommi Gunn" (London 
Night Studios; the actual date is 11/96 but ComicVine doesn't have it) listed 
as issue "1/2". 

Original comment by olin...@gmail.com on 7 Dec 2013 at 10:45

GoogleCodeExporter commented 9 years ago
Finally looked into this one.  Should be fixed with next release

Original comment by bevi...@gmail.com on 22 Mar 2014 at 8:34

GoogleCodeExporter commented 9 years ago

Original comment by bevi...@gmail.com on 25 Mar 2014 at 10:23