albums with "special" chars cause exception when doing freedb lookup in cli program

[GoogleCodeExporter]

1) Please describe the steps to reproduce the situation:

a.  insert a CD with non-latin characters in file/track names

b.  do rrip_cli -d

c.  program raises exception

2) What is the expected output? What do you see instead?

I expect it to try to do a lookup, even if not found to try to rip with 
"unknown"  values. Instead an error "/rr_lib.rb:1470:in `expand_path': 
incompatible character encodings: ASCII-8BIT and UTF-8 
(Encoding::CompatibilityError)" occurs and the program exits.

3) What version of rubyripper are you using? On what operating system? The
gtk2 of commandline interface?

See attached file. System is Debian Wheezy on an eeepc.


4) Is this not already fixed with the latest & greatest code? See for
instructions the Source tab above.

5) Does the problem happen with all discs? If not, please attach
the output of cdparanoia -Q with a disc that gives trouble.

No, only ones that have non-latin chars. No cdparanoia attached as that is 
totally unrelated. This is a freedb lookup issue.

6) Please explain why this change is important for you. Also, how many
users would benefit from this change?

no idea. It's  a bug. Affects approximately 1 in 250 CD's. Annoying though 
because if I rip a stack of CDs automatically, I can't be sure they all  got 
ripped, so I have to manually catch this somehow.

Please provide any additional information below. The more usefull
information provided, the sooner the issue will be fixed.

Note that ruby versions older than 1.9 are no longer supported. You are
advised to upgrade instead.

Original issue reported on code.google.com by [email protected] on 23 Dec 2014 at 6:32

Attachments:

• rrcli_utf8_bug.txt

[GoogleCodeExporter]

in fact this issue DOES seem to be fixed in latest and greatest code. Thanks 
and sorry for the erroneous report!

Original comment by [email protected] on 23 Dec 2014 at 6:40