Earlier versions of tracewpp avoided Unicode conversions and performed text processing assuming a single-byte character set. Behavior change: tracewpp now converts all input text to Unicode, performs processing in Unicode, and converts output text to the specified output encoding.Use command-line parameters -cp:UTF-8 or -cp:UTF-16 to generate Unicode output files. By default, output files will be encoded using the current code page (CP_ACP). For backwards-compatibility, if the -UnicodeIgnore command-line parameter is specified, files starting with a UTF-16 BOM will be treated as empty. Input files that do not start with a BOM will be read using the current code page (CP_ACP). Input files starting with a UTF-8 or UTF-16 byte order mark (BOM) will be read as Unicode. Windows Trace Preprocessor (tracewpp.exe) updates: cpp file instead of arbitrarily picking one or the other). cpp files with conflicting definitions of MCGEN_EVENTWRITETRANSFER are linked into the same binary, the MC-generated ETW helpers will now respect the definition of MCGEN_EVENTWRITETRANSFER in each. Now avoids one-definition-rule (ODR) problems in MC-generated C/C++ ETW helpers caused by conflicting configuration macros (e.g.Otherwise, it will be read using the current code page (CP_ACP). If the -u parameter was specified, it will be read as a UTF-16LE file. Otherwise, if it starts with a UTF-16LE BOM, it will be read as a UTF-16LE file. mc file starts with a UTF-8 BOM, it will be read as a UTF-8 file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |