Compilation errors and printout garbled problems caused by Chinese content in vs2019 code

Preface

stay VS2019 in , If the code contains Chinese string definitions or comments , It will lead to all kinds of inexplicable compilation errors , Even if you are lucky , There is no error in compilation , You will also encounter the problem of printing Chinese garbled codes on the console , It makes people feel irritable .

Compilation problems

1. Chinese string constants are defined in the code, resulting in compilation errors ：“ Line breaks in constants “ ;
2. The code contains Chinese comments, which leads to compilation errors ： Can't find XXX ( macro 、 Variable )、XXX Is not a constant / Variables and other problems caused by missing declarations ;

The problem of printing garbled code

Code print Chinese string , The output at the command prompt is garbled ;

resolvent , Choose one of the three methods ：

One . Modify the code file format to utf-8 Signed , Give Way MSVC The compiler can automatically recognize and utf-8 BOM Format load file ：

1. Use an external editor to save the code file as utf8-BOM Format ;
2. or Open the code file , stay VS2019 “ Advanced save options ” Select the code file saving format as “Unicode- Signed “;
   

Two . Change the code format ：

Modify Chinese string 、 Format of Chinese Notes , Add English space at the end of Chinese , Give Way MSVC The compiler can use GBK Code loading and compiling Chinese utf-8 Encoded string , It can solve the problem of compilation errors , Print or garbled ;

3、 ... and . Force the designation of MSVC The encoding format of the code file loaded by the compiler ：

1. stay VS2019“ project ”-“ Engineering properties ” Dialog box -“C/C++”-“ All options " Subpage , stay “ Additional options ” Add in “/utf-8” ( Equate to ”/source-charset:utf-8 /execution-charset:utf-8");
2. stay VS2019“ project ”-“ Engineering properties ” Dialog box -“C/C++”-" All options " Subpage , stay “ Additional options ” Add in “/source-charset:utf-8 /execution-charset:gbk” ( The former represents the encoding of the file itself , The latter indicates the encoding of bytes in the compiled character array );
   

summary ：

1. If it's a new project , Recommended method 1 , Let all new code files be unified as utf-8 BOM Format ;
2. If it is cross platform code , And the document contains a small amount of Chinese Notes , You can try method 2 ;
3. If it is an existing historical complex project （ Solutions that are not exported using tools ）, You can try method 3 , But you need to pay attention to the settings execution-charset when , Consider at the same time UI Requirements for string encoding of both display and print （ It may not be the same ）;

reference information ：

• 1VS2019 Report errors “ Line breaks in constants ” Error cause analysis
• 2 MSVC file - Set the source and execution character sets to UTF-8
• 3vs Chinese notes can't be compiled