Unicode string means generally UTF-16. UTF-16 could be Le or Be.
And FPC always uses the endianess of the target, so it makes no sense to talk about UTF-16BE vs. UTF-16LE in the general sense in the context of FPC.
Some people speaks, wrong, Unicode string for UTF-8. Please, use the exact denomination...
We are on a FPC/Lazarus forum here, so I can assume that the users know when I write “UnicodeString” that I mean
UnicodeString which in turn means UTF-16 (no matter if BE or LE) and not “Unicode string” which might mean any string with a Unicode encoding.
Unicode string means generally UTF-16. UTF-16 could be Le or Be.
Some people speaks, wrong, Unicode string for UTF-8. Please, use the exact denomination...
It is the other way around. MS uses unicode 16 (based on UCS) and the rest of the world uses UTF8.
Qt uses UTF-16, JavaScript uses UTF-16, Java uses UTF-16. And on non-Windows
wchar_t is even four Byte and thus uses UTF-32.