utf-8 support in sdk/plugin api

[fpefpe]

is there a new api/sdk layer to support UTF in the api calls?

 

[Charles Dye]

If you use Printf(), Qprintf(), and QPuts(), output will be according to the //UnicodeOutput and //UTF8Output option settings. (It's worked that way for the last several versions.)

As for reading input from a file, I think you need to handle that yourself. One way is to call MultiByteToWideChar() with CodePage set to CP_UTF8.

 

[fpefpe]

so all the sdk/plugin api call are still unicode (16 bit) calls?

 

[Charles Dye]

Truth be told, I hadn't even looked at the new SDK. Now that I do look, I see a couple of functions which I don't remember seeing before:

void WINAPI UnicodeToUTF8( LPCWSTR pszUnicode, char * pszUTF8, int nLength );
/* 
    Convert a Unicode string to UTF8
    nLength = maximum length of pszASCII
*/

void WINAPI UTF8ToUnicode( const char * pszUTF8, LPWSTR pszUnicode, int nLength );
/* 
    Convert a UTF8 string to Unicode
    nLength = maximum length of pszUnicode
*/

I don't know what they do that you can't do with WideCharToMultiByte() and MultiByteToWideChar(), though.

 

[rconn]

All of the Windows API calls & the TCC plugin API calls are UTF16. If you want UTF8 you'll need to do the translation yourself.