Hi. I am having a little problem with Debian Lenny and Amarok 1.4.9.1.

I am listening to an excellent selection of music in www.cafecody.com, which I added as a stream from:

Code: Select all

<url>http://cafecody.com/listen.m3u</url>

However, the stream sends information about the song and I cannot modify this (i.e. I cannot use easytag or some other software because this is not my own collection of files). When the info sent has only ASCII characters, there is no problem, but when it has accented characters, they do not show properly. e.g.:

as found in ~/.kde/share/apps/amarok/current.xml

Code: Select all

<Comment>Melibea - Fusion - Café del Mar Dream 4  5-22</Comment>

where it should be

Code: Select all

<Comment>Melibea - Fusion - Café del Mar Dream 4  5-22</Comment>

Is there any way to correct this?

My language setting is:
en_US.UTF-8

P.S. i have another similar issue with my laptop, also in Debian Lenny, but the charset is even worse:
as found in ~/.kde/share/apps/amarok/current.xml

Code: Select all

<Title>Chavari Agrable - Two Upon - Ennemond Gaulter - La Pompe F</Title>

What version of taglib are you using?

If i had to guess I would bet the metadata being sent with the stream does not specify the encoding as unicode (which it probably is).

I am using, acording to aptitude:

Package: libtag1c2a
State: installed
Automatically installed: yes
Version: 1.4-8.1
Priority: optional
Section: libs

and

Package: libtagc0
State: installed
Automatically installed: yes
Version: 1.4-8.1
Priority: optional
Section: libs

My guess is that too... i already sent a question to the site, asking for more info... but meanwhile, supposing it is something with the stream, is there any way to fix it? or a workaround? I ask because, specially in the notebook, the use of those characters is not properly handled by the Jabber + Now Listening plugins, and my jabber account disconnects every time there are strange chars in the stream, with a 'Malformed stream packet recieved' error.

Wow... when I was writing the previous post, the library was updated to version 1.5-2! hahaha... what a coincidence... I will check if that works...