Closed wader closed 8 years ago
Ah yes, that's annoying. Although the standards are remarkably vague, it's very frustrating that some implementations chose to ignore the more well-defined parts!
My only hesitation here would be that we should really have some "config" to decide the default byte order when no mark is found. I do have an idea for a patch, so I'll put it in a separate branch and mention it here when done.
Yeah hmm :( my guess is little endian is most common... some utf16 buffer on a x86 machine. Let me know when you push the branch.
Header from BBC podcast: r4choice_20131004-1530a.mp3.header.zip
Thanks for the header data, made it much easier to test.
I've put my changes straight into master. Not hugely elegant, but it will fix your problem and is much better than just returning an error.
Thanks, works great!
Hi, i have some mp3 files (BBC radio podcasts) that have UTLS frames with encoding type 1 but no BOM. They have string data in UTF16 little endian.
Do you think it's worth even trying to do some kind of fallback?