What code pages, what are you talking about? The "special codes" define the number of bytes to encode a character because the encoding is of variable length. UTF-8 can encode any Unicode character as well as UTF-16. And utf-16 with variable length (surrogate pairs).
The task of discussing Unicode is not the task here.
Exactly, different platform architectures, that's why on Windows everyone says UTF-16LE/BE Because the Windows terminal is written for Windows, got it ))
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
What code pages, what are you talking about? The "special codes" define the number of bytes to encode a character because the encoding is of variable length. UTF-8 can encode any Unicode character as well as UTF-16. And utf-16 with variable length (surrogate pairs).
The task of discussing Unicode is not the task here.
That's not all.
As ANSI Cyrillic = CP1251, so
Unicode:
UTF-8 = CP65001, // UNIX/Linux
UTF-16LE = CP1200, // Windows
UTF-16BE = CP1251,
UTF-32LE = ?
UTF-32BE = ?
ISO10646:
UCS-2 ~ UTF-16
UCS-4 = UTF-32
Confusion? No, we haven't.
Exactly, different platform architectures, that's why on Windows everyone says UTF-16LE/BE
Because the Windows terminal is written for Windows, got it ))
It's a pity ArraySwap can't do that.
To enable profiling the EA on real data, I add these lines to it.
What's wrong with manually stopping the profiler?
What's wrong with manually stopping the profiler?
Manual stop does not produce profiling results, unfortunately.
Manual stop does not produce profiling results, unfortunately.
There must be a problem with the code. It works for me.
Manual stop does not produce profiling results, unfortunately.
Same problem.
Yes, I have the history reading present.