for example - if I have LPWSTR or LPTSTR or even wchar_t variable -
and I would like to add into these strings or assign the single variable the unicode character which code is u+1f37a (beer mug) - how do I do it ? I tried looking for code->character function in the winapi but i did not find any.
any ideas guys?
thanks in advanced.
In C99 you can encode the data as a universal character name.
That creates a string which will contain the beer glyph, not counting the terminating 0.Code:wchar_t beer_mug[] = L"\U0001f37a";
I'm trying to compile the line you gave as C++11 code, and the compiler gives the error:
[Error] int-array initialized from non-wide string
trying to use the line as
only makes it appear as a Chinese character, rather than a beer mug ( :) )Code:wchar_t beer_mug = '\U0001f37a';
edit:
I will also add that in my code , i have the unicode macros:
Code:#ifndef UNICODE
#define UNICODE
#endif
#ifndef _UNICODE
#define _UNICODE
#endif
A couple of things:
First, not all unicode characters are just one character. To be specific, UNICODE unambiguously refers to glyphs as code points, and certain encodings will require different memory space from the same data. The code point itself would be represented in 4 bytes. A UTF-16 encoding would require 2 wchar_t characters, for example. The data was meant to be encoded as a string like I showed you. That said, I did make a mistake: I forgot to prepend my quotes with an L. You can now see that I corrected myself above.
You can rest assured that \U0001f37a unambiguously refers to beer. :D
Second, is that you will have to use a font that supports the beer glyph to actually see it. You can see a list here. When I just try to use it, it prints nothing like a beer mug, but not all fonts have that glyph in the first place. Actually seeing the glyph would require more WinAPI code, and unfortunately, I'm not prepared to give that to you. I need time to do more research and see what works.
the rendering of the gylphs was solved when I created font-handle from "symbola" and sending it through "WM_SETFONT" which made all the glyphs render perfectly!
thank you very much!
I can't really add anything, but I had a question for y'all. Do you specifically use the wchar_t type when using Unicode, or do you use the TCHAR?
I ask because I'm reading "Programming Windows" (5th ed.), and all the programs use TCHAR (and the TEXT token paste macro), but it's a bit old so I wasn't sure if people nowadays were just using nothing but Unicode or something.
TCHAR just resolves to wchar_t when you define _UNICODE and build. I was specifically talking about wchar_t so I didn't bother. In a real program, its only use is porting programs to non-Unicode supporting platforms.
I see, thanks. Yeah, the book actually has a whole chapter on the whole _UNICODE definition thing. The idea seemed pretty clever to me, although I didn't really get why they needed to make redefinitions of the symbolic constants they were using.Quote:
Originally Posted by whiteflags
For instance the TEXT macro starts off as __T, and then later gets a redefinition for convenience to _T, then in another place to TEXT. I wonder why they just didn't call it TEXT to begin? lol.
O_oQuote:
For instance the TEXT macro starts off as __T, and then later gets a redefinition for convenience to _T, then in another place to TEXT. I wonder why they just didn't call it TEXT to begin?
Because they were born with unique usage in mind as a form of documentation.
At least, that is what some Microsoft employees have said. I'd find it more likely that programmer Fred created `_T' due to being unaware that programmer Bob had made `TEXT' for the same purposes.
Soma
I understand it as: one is for the CRT, and one is for the Win32 API.
"TEXT" (and "UNICODE" used) in WinNT.h.
"_T", "_TEXT" (and "_UNICODE" used) in tchar.h.
[edit]Ah, "leading underscore followed by uppercase reserved for the impl." - I'm guesing[/edit]
gg