Bug #580

BOM-Bytes in UTF8 encoded files ignored

Added by xyz dragon over 1 year ago. Updated over 1 year ago.

Status:Closed Start date:October 16, 2015
Priority:Minor Due date:
Assignee:- % Done:

100%

Category:-
Target version:3.7
Affects version:3.5.2

Description

I have several .m3u-playlists saved from mpc on Windows, which seems to be saved as UTF8 with BOM (used hexeditor seeing the ef bb bf bytes).
The problem is, when trying to import such an playlist, the first track won't work, because audacious thinks the BOM-bytes are part of the file path.
Actually this can be seen by right clicking on first track > properties -> copy full path shown -> paste into terminal and send to hexdump -> ef bb bf bytes show up even int that copy>pasted string. As those 3 bytes are not visible it was quite a witchcraft to see at work: one command working, the other not (tried to test la $filepath), but both looking exactly the same.

echo '/media/d/OSTs/Se/./mimi.mp3' | hexdump -C | grep 'ef bb bf'

I'm not sure whether this will work after posting it, but in the edit-window writing this, I can copy paste the command and see grep returning a result for the BOM bytes. As I use relative paths the bytes are before the dot.

Associated revisions

Revision 4b1ee2d0
Added by John Lindgren over 1 year ago

m3u: Skip over UTF-8 byte order mark. Closes: #580.

History

#1 Updated by John Lindgren over 1 year ago

  • Status changed from New to Closed
  • Target version set to 3.7
  • % Done changed from 0 to 100

Fixed.

#2 Updated by xyz dragon over 1 year ago

Thank you for that lightning fast fix. I installed from source and it works. Furthermore the upgrade from 3.5.2->3.7 now finally has the standard xfce-look instead of the GTK3-Look.

Also available in: Atom PDF