标签：use code elusive non will cannot correctly those
This problem can cause the following elusive bugs by AUTOMATIC ENCODING CONVERSION without any warnings or errors:
- Cannot read or write strings of the type WCHAR , LPCWSTR... correctly; can not declare any non-English wchar_t with the format of L"おかしい" correctly. e.g: L"正£" cannot be correctly received by the windows API. You cannot easily notice that since you check the memory\the variables, those wchar_t variables are correctly encoded into UTF-16LE. But those variables cannot be correctly passed between services. If you only use those WChar[] in your program without calling any APIs, everything will be ok.
- Cannot use the CString correctly. CString st = _T("正£"); will actually create L"æ£Â£"
- Cannot use Windows API correctly: the API can receive and use those arguments without any warnings, yet non-ASCII bytes will be combined together to trigger unexpected behavior.
- In SAPI5, you can speak English text but cannot speak non-English text correctly. Strange symbols like öüäü€＄ will be spoken.
Solution:
Change the encoding of the source files(e.g: Source.cpp) into UTF-16LE WITH BOM
标签：use,code,elusive,non,will,cannot,correctly,those 来源： https://www.cnblogs.com/xuesu/p/16663923.html
本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享； 2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关； 3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关； 4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除； 5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。