| Newsgroups |
gmane.comp.audio.eac.user |
| Message-ID |
<[email protected]> |
Michael wrote:
> As explained here
>
> https://hydrogenaud.io/index.php/topic,117467.0.html <https://hydrogenaud..io/index.php/topic,117467.0.html>
> it seems that EAC writes the cue file with BOM, which prevents Foobar2000 from understanding the cue file directly.
>
>
>
> It also seems that BOM is not recommended so I am wondering if there is a way to not have EAC use it, I did not find one in the options however.
>
Two points:
Not recommending a BOM is not the same recommended against a BOM. By analogy, a fire extinguisher is not recommended for my car by the manufacturer, but that doesn’t mean that adding one goes against manufacturer recommendations, will cause the car to malfunction, or that it is a bad thing to do.
What "prevents Foobar2000 from understanding the cue file directly” is deficiencies in Foobar2000. According to the Unicode Standard 5.0, BOM is allowed for UTF-8, UTF-16, and UTF-32 encoding (see Table 2-4. The Seven Unicode Encoding Schemes). If Foobar2000 can’t handle a BOM in all of those cases, then Foobar2000 is FUBAR.
I recommend that you read this insightful 2015 thread on Foobar2000 and BOM:
https://hydrogenaud.io/index.php/topic,107959.0.html
Regards,
Fred Maxwell
Moderator, Exact Audio Copy Yahoogroup