From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
According to the freedb FAQ, entries must be submitted in ISO-8859-1 format, not
in UTF-8, which we use by default. The wire protocol goes both ways: if I
retrive entries with non-ASCII characters with grip running in a UTF-8 locale,
it gets very confused. It should convert entries downloaded in iso-8859-1 to
the locale representation, and convert back to iso-8859-1 when submitting new
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start grip in a UTF-8 locale
2.Attempt to register a CD with a non-ASCII character in its title
3.Do it again in a iso-8859-1 locale.
4.Restart grip in a UTF-8 locale.
5.Retrieve the entry
Actual Results: For 2, You get an e-mail back stating that an invalid character
set was used. For 5, you get back a mangled entry.
Expected Results: The e-mail contents should be generated in iso-8859-1, and
downloaded entries should be converted back from iso-8859-1 to the chosen
locale. The wire protocol specifies iso-8859-1.
Unfortunately, choosing a non-UTF8 locale means you have to drop non-ASCII
characters from filenames, which often makes song titles unreadable.
I'm probably not going to get to this very soon. Feel free to file upstream at:
was reportedly fixed on Oct 1, but AFAICT there isn't any newer stable release
containing hte patch. I haven't looked at the patch to see whether it would be
easy to back-port, but it pobably isn't worth doing anyway.
grip is no longer shipped in the development tree; as such, it is unlikely older
bugs will be fixed.
I thought it was being pushed to extras, not simply dropped. Anyhow,
I believe the problem is fixed in FC3.