Bug#526826: rhythmbox: wrong encoding when browsing the content of a mt-daapd server

[Tino Keitel]

On Mon, May 04, 2009 at 20:10:07 +0200, Tino Keitel wrote:
> On Mon, May 04, 2009 at 10:20:01 +0200, Josselin Mouette wrote:
> 
> [...]
> 
> > How is mt-daapd configured wrt. filenames encoding? If it is assuming
> > they are in ISO8859-1(5), this would lead to this exact result.
> 
> I can not find any charset related settings in mt-daapd. I also found
> out that not all metadata is broken, only some of it. I took a dump of
> the network traffic to the mt-daapd server to see what actually goes
> wrong, but the broken metadata seems to be completly encoded so I
> coulnd't find in in the cleartext.

My network dump was incomplete. I tried it again and got a complete
dump of the network traffic.  I saw that the metadata provided by
mt-daapd is already broken.  At the end, I found out that some broken
software seems to have written broken ID3v2.3 tags.  The encoding is
latin_1, but the content is encoded in UTF8.  This is wrong in 2
points:

1. the encoding of the text is wrong

2. ID3v2.3 doesn't even support UTF8, only UTF16

This doesn't seem to be a problem for local files in Rhythmbox (it
actually _should_ be a problem, since the encoding in the mp3 files is
totally wrong, and data corruption is hidden this way), but mt-daapd
seems to respect the encoding settings.

I guess this bug can be closed. However, I'd still like to know what
software part decodes the metadata information for local files, since
it doesn't seem to respect the encoding settings.

Regards,
Tino