BOM in m3u8 files raise an error

MissingSample ...

Including a BOM in a file format that's explicitly UTF-8 seems like a gratuitious bad idea though - this just shows why...

assigned to @Courmisch

added Component::Demuxers: Playlist label

I ain't deliberately inserting the BOM. Some (legit) CD ripping software (EAC for instance) have been producing UTF8+BOM files for years. And an UTF8 file may include a (legit) BOM.

What's surprising and irritating is that successive VLC versions have, more or less randomly from a user point of view, considered the BOM as either something unsignificant and normal or a blocking error.

Replying to [comment:2 jchd]:

I ain't deliberately inserting the BOM. Some (legit) CD ripping software (EAC for instance) have been producing UTF8+BOM files for years. And an UTF8 file may include a (legit) BOM.

What's surprising and irritating is that successive VLC versions have, more or less randomly from a user point of view, considered the BOM as either something unsignificant and normal or a blocking error.

What's suprising is that's that might not be the bug you're pointing out. M3U can go thoruhg adaptive or playlist, and restrictions are different, hence the need for sample

All I can say is that the latest version (3.0.6 Win-x86) I installed errors out when .m3u8 files have a BOM, and doesn't anymore when I edit the .m3u8 file to UTF8-noBOM format.

Previous versions either barked at the BOM or not, depending on the version.

I make a very basic use of VLC here: I rip my CDs to .flac + m3u8 using EAC and double-click on the m3u8 file or single record when desired, that's it.

VLC should be as smart as possible and always check the presence of BOM.\ .m3u8: BOM or no BOM => UTF8\ .m3u: BOM => UTF8; no BOM => not UTF8

Depending on extensions is a very bad idea.

added 1 deleted label

added Status::fixed label

changed milestone to %4.0

closed

BOM in m3u8 files raise an error

Child items 0

Activity