- Status Closed
- Percent Complete
- Task Type Bugs
- Category ID3 / meta data
-
Assigned To
learman - Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#7698 - ID3 "Comment" field not correctly displayed (and read?)
The comment field in the attached file should be “ÄÖÜäöüß” (German umlauts; the problem also occurs when e.g. cyrillic letters are used). But in “Show ID3 Info” screen it is shown as in the attached image. The font used is nimbus-14, it contains the appropriate glyphs (so it’s because of the bad font).
I don’t know whether this is a problem with ID3 reading or just displaying.
Observed in r14585.
bad_comment.mp3
bad_comment.bmp
Closed by learman
2007-09-03 16:15
Reason for closing: Fixed
Additional comments about closing:
2007-09-03 16:15
Reason for closing: Fixed
Additional comments about closing:
UTF-16 comments weren't read
correctly.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
The comment field, rather surprisingly I think, has a BOM. I suppose Rockbox could strip those from comment fields. I don’t know if your tag is technically broken or not. It’s also UTF-16.
ff fe c4 00 d6 00 dc 00 e4 00 f6 00 fc 00 df 00
In the original report, it should read “so it’s _not_ because of the bad font” of course.
I don’t know anything about the ID3 standards but the tag is correctly displayed in Windows Explorer (file properties), Media Monkey, and Mp3Tag.
Another thought: the presence of the BOM is a sign that the field is UTF-16 encoded (not UTF-8) since UTF-8 doesn’t need any byte order. So the correct handling of this should be done in RB. Maybe also for other fields (I don’t know if the code is the same for all fields).