Исходное сообщение
"В OpenBSD будет удалена поддержка всех локалей, за исключени..." Отправлено Stax, 15-Авг-15 12:29
Здравомыслящим програмистам? Из официального unicode faq: Q: When would using UTF-16 be the right approach? A: If the APIs you are using, or plan to use, are UTF-16 based, which is the typical case, then working with UTF-16 directly is likely your best bet. Converting data for each individual call to an API is difficult and inefficient, while working around the occasional character that takes two 16-bit code units in UTF-16 is not particularly difficult (and does not have to be expensive). Q: How about converting to UTF-32? A: If your platform or i18n library supports UTF-32 (4-byte) characters, then, for similar reasons, you might want to use them instead of UTF-16. Generally, the simplest approach is to match your basic character and string datatype to that used by the APIs you need to call. However, UTF-32 is often a poor choice for high performance, since (on average) only half as many characters will fit your processor cache. Many libraries, such as ICU or Java 5, use a hybrid approach. For strings, they use UTF-16 to reduce storage, but for single-character APIs they use code points (UTF-32 values) for API simplicity.