Incorrect parsing of utf16 byte order mark

Bug #550056 reported by MMauka
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libid3tag (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu 9.10
Release: 9.10

libid3tag0:
  Installed: 0.15.1b-10build1
  Candidate: 0.15.1b-10build1
  Version table:
 *** 0.15.1b-10build1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Expected: Correctly parse mp3 file with big endian UTF16 tags so tags such as
title and album name show up in gtkpod corrrectly.

Instead: In gtkpod the mp3 text fields such as title and album name show with
Chinese characters.

Root cause: The mp3 file has string fields with two byte order marks. The correct
one is the second one.

0000000: 4944 3303 0000 0006 4a2a 5441 4c42 0000 ID3.....J*TALB..
0000010: 001f 0000 01ff fefe ff00 5300 6500 6300 ..........S.e.c.
                     ll llbb bb

llll = little endian byte order
bbbb = big endian byte order

libid3tag utf16.c:id3_utf16_deserialize() assumes there is only one.

Revision history for this message
MMauka (buasst) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.