+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1)
+--- Forum: Code and Stuff (https://qb64phoenix.com/forum/forumdisplay.php?fid=3)
+---- Forum: Help Me! (https://qb64phoenix.com/forum/forumdisplay.php?fid=10)
+---- Thread: GetWindowTextW - can you get it to work? (/showthread.php?tid=2784)
Pages:
1
2
RE: GetWindowTextW - can you get it to work? - TerryRitchie - 06-10-2024
Yikes, lots to learn. Thanks for the Unicode info.
RE: GetWindowTextW - can you get it to work? - SMcNeill - 06-11-2024
(06-10-2024, 09:30 PM)TerryRitchie Wrote: Yikes, lots to learn. Thanks for the Unicode info.
Early adoption of UCS-2 ("Unicode 1.0") led to common use of UTF-16 in a number of platforms, most notably Microsoft Windows, .NET and Java. In these systems, it is common to have a "wide character" (wchar_t in C/C++; char in Java) type of 16-bits. These types do not always map directly to one "character", as surrogate pairs are required to store the full range of Unicode (1996, Unicode 2.0).
RE: GetWindowTextW - can you get it to work? - SpriggsySpriggs - 06-11-2024
With Unicode, however, you can handle foreign characters sets like Korean, Japanese, and Chinese. You wouldn't necessarily be able to parse the information from those but you'd be able to display them in titles and other Win32 objects. But, again, it's a hassle. If you ever choose to venture out into The Land of Wide Strings, let me know. I have intimate experience with them. Many a sleepless night and head banging session (not the rock music kind. The brick wall kind)