Thorium wrote:Would be even better if PB would use UTF-16 internaly instead of UCS-2.
It would have the same problem you ran into with UTF-8 (making some string procedures more complicated and most likely slower).
It also would break existing forum code which uses pointers to unicode characters assuming a unicode character always takes up two bytes.
Thorium wrote:Would be even better if PB would use UTF-16 internaly instead of UCS-2.
It would have the same problem you ran into with UTF-8 (making some string procedures more complicated and most likely slower).
It also would break existing forum code which uses pointers to unicode characters assuming a unicode character always takes up two bytes.
I know. The reason is WinAPI as mhs and Little John wrote. With UCS-2 there is not a 100% compatiblity to the WinAPI.
hope:
1 add AsciiToUni(),UniToAscii(),...
2 string is data,isnot string
3 AsciiToUni(),UniToAscii(),...result immobile data
4 Strings functions no only for string,Example:
FindString() changeTo FindData(a.data,b.data,wordBeyes)
Flag:wordBeyes=1 or 2 or 3 or 4 or 5 or ...
use Strings functions,you must know your data Structure
==============
other Note:Unicode in win32.hlp[1997]
Example:
EM_SETSEL
Windows NT: Yes
Win95: Yes
Win32s: Yes
Import Library: -
Header File: winuser.h
Unicode: No
Platform Notes: None
EM_EXSETSEL
Windows NT: Yes
Win95: Yes
Win32s: No
Import Library: -
Header File: richedit.h
Unicode: No
Platform Notes: None