Specifies the execution character set used for string and character literals. This directive is not needed for literals marked with the u8 prefix.
Specifies the target execution character set. Currently the only target execution set supported is "utf-8".
This compiler directive is obsolete starting in Visual Studio 2015 Update 2. We recommend that you use the
/utf-8 compiler options together with using the
u8 prefix on narrow character and string literals that contain extended characters. For more information about the
u8 prefix, see String and Character Literals. For more information about the compiler options, see /execution-charset (Set Execution Character Set) and /utf-8 (Set Source and Executable character sets to UTF-8).
#pragma execution_character_set("utf-8") directive tells the compiler to encode narrow character and narrow string literals in your source code as UTF-8 in the executable. This output encoding is independent of the source file encoding used.
By default, the compiler encodes narrow characters and narrow strings by using the current code page as the execution character set. This means that Unicode or DBCS characters in a literal that are outside the range of the current code page are converted to the default replacement character in the output. Unicode and DBCS characters are truncated to their low-order byte. This is almost certainly not what you intend. You can specify UTF-8 encoding for literals in the source file by using a
u8 prefix. The compiler passes these UTF-8 encoded strings to the output unchanged. Narrow character literals prefixed by using u8 must fit in one byte, or they are truncated on output.
By default, Visual Studio uses the current code page as the source character set used to interpret your source code for output. When a file is read in, Visual Studio interprets it according to the current code page unless the file code page was set, or unless a byte-order mark (BOM) or UTF-16 characters are detected at the beginning of the file. Because UTF-8 can't be set as the current code page, when the automatic detection encounters source files encoded as UTF-8 without a BOM, Visual Studio assumes that they are encoded by using the current code page. Characters in the source file that are outside the range of the specified or automatically detected code page can cause compiler warnings and errors.
We’d love to hear your thoughts. Choose the type you’d like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.