Hello, On penktadienis 04 Rugsėjis 2009 13:42:19 you wrote: > It looks like Amarok 2.1.1 can't even read the tags at all. If I right > click on the song, go to Edit Track Details, Tags, then all the > fields are empty, besides Genre, which is Blues. Also, the song > doesn't show up at all, when I search for it's details in the music > collection. > > Interestingly, mp3info doesn't find any tags either, but the 'extract' > shows the tags correctly. > Audacious and Audacity show a bunch of gibberish :-/ > I'm guessing that the unicode used in the tag headers is fairly > nonstandard.
I don't think it is fair to request Amarok to somehow magically support broken tags, is it? Looking at the tag info you provided, it is evident they do not follow standard ID3v2 standard. They indicate encoding UTF-16 with BOM for text fields (byte 01) while actually the text has no BOM. So there is no surprise Amarok 1 used to "cut" the first letter. Apparently, Amarok 2 is even more strict and since there is no valid BOM sequence, it does not decode those fields at all. > I'm not sure how to re-open, or if replying does that automatically. > Or should I report this as a new bug? Do not file a new report. I will reopen the bug if you can provide me proof that Amarok is at fault here. -- Modestas Vainius <[email protected]>
signature.asc
Description: This is a digitally signed message part.
