Windows Clipboard won't preserve ASCII character - c++

Question

I am writing a plugin for the TS3 Client, but I ran into an issue...
One of the channel names has a special sign (╠) in it, which is a special character from the extended ascii table I think.
When logging it INSIDE teamspeak, the character shows fine, but when trying to copy it to the windows clipboard using its C interface it returns a whole different character (â).
I have tried converting it to WCHAR after I read that the extended ascii table uses more bytes than the regular char, but that didn't work either.
I use the following code to copy the char* to the clipboard which I found somewhere and altered with some other code I found for using WCHAR:
void SaveClipboard(char* tx)
{
WCHAR text[140];
swprintf(text, 140, L"%hs", tx);
if(OpenClipboard(NULL))
{
EmptyClipboard();
HGLOBAL global = GlobalAlloc(GMEM_DDESHARE, 2 * (wcslen(text) + 1)); //text size + \0 character
WCHAR* pchData;
pchData = (WCHAR*)GlobalLock(global);
wcscpy(pchData, text);
GlobalUnlock(pchData);
SetClipboardData(CF_UNICODETEXT, global);
CloseClipboard();
}
}

Answer 1

wchar_t is UTF-16 encoded, but the data you get is UTF-8 encoded. You don't convert between these two encodings, you simply reinterpret the bytes.
Looking at the code points for those characters it should become obvious what's happening: The UTF-8 code point for ╠ is 0xE2 0x95 0xA0 and the UTF-16 code point for â is 0x00 0xE2, while the UTF-16 code point for ╠ is 0x25 0x60.
swprintf(text, 140, L"%hs", tx); <- This simply converts each char into a wchar_t, turning the 3 byte UTF-8 code point 0xE2 0x95 0xA0 into three 2 byte UTF-16 code points: 0x00 0xE2, 0x00 0x95 and 0x00 0xA0.
To get 0x25 0x60 from 0xE2 0x95 0xA0 you need to actually convert the data:
std::wstring_convert<std::codecvt_utf8_utf16<char16_t>> converter;
std::wstring text = converter.from_bytes(tx);
Alternatively, since you are using WINAPI already, you can use MultiByteToWideChar:
WCHAR text[140];
int length = MultiByteToWideChar(CP_UTF8, 0, tx, -1, (LPWSTR)text, 140);