The Unicode character ń (U+0144) is displayed as Å„ (U+00C5 U+201E). What's wrong here? fb2k doesn't seem to recognise the cue sheet as a Unicode file (I use UTF-8)? I thought foobar2000 can at least read Unicode cue sheets...
In UTF-8 the character \u0144 is not 0x0144 but 0xC584 because it uses this special encoding for distinguishing it from the ASCII characters. But instead of interpreting the two byte sequence correctly fb2k simply displays the corresponding chars according to the Windows codepage: Å (0xC5) „ (0x84).
Btw, I now see that UltraEdit's so called "Unicode" format is actually the UTF-16 format, hehe. This Unicode encoding consequently uses two bytes per character or more when it's a "very high leveled" character, and at the beginning is a header called BOM, but the UTF-8 format characters are only one byte for normal 7bit-ASCII characters and when there's a Unicode character it uses two bytes with a special bit level recoding. That's why fb2k thinks it's not Unicode but an 8-bit Windows text file? It doesn't sees a BOM maybe?
Heh, no. Unfortunately the cue sheets in double+ byte Unicode format UTF-16 (as I said it's called "Unicode" by UltraEdit and not "UTF-16" in contrast to "UTF-8"
) fails to load completely... So there's no support for Unicode cue sheets in foobar 0.9.4.1?
EDIT: Ah, I got it! UltraEdit was set to save UTF-8 without a BOM (0xEF 0xBB 0xBF)...