Skip to content

Commit cc7698b

Browse files
author
Colin Robertson
committed
Clean up walkthrough, add some Vcpkg goodness
1 parent 89d66ab commit cc7698b

File tree

5 files changed

+548
-453
lines changed

5 files changed

+548
-453
lines changed
Lines changed: 35 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1,49 @@
11
---
22
title: "Unicode Support in the Compiler and Linker | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "11/04/2016"
5-
ms.reviewer: ""
6-
ms.suite: ""
4+
ms.date: "12/15/2017"
75
ms.technology: ["cpp-tools"]
86
ms.tgt_pltfrm: ""
97
ms.topic: "article"
108
f1_keywords: ["VC.Project.VCLinkerTool.UseUnicodeResponseFiles", "VC.Project.VCLibrarianTool.UseUnicodeResponseFiles", "VC.Project.VCCLCompilerTool.UseUnicodeResponseFiles", "VC.Project.VCXDCMakeTool.UseUnicodeResponseFiles"]
119
dev_langs: ["C++"]
1210
helpviewer_keywords: ["Unicode, Visual C++"]
13-
ms.assetid: acc1d322-56b9-4696-a30e-2af891a4e288
14-
caps.latest.revision: 10
1511
author: "corob-msft"
1612
ms.author: "corob"
1713
manager: "ghogen"
1814
---
1915
# Unicode Support in the Compiler and Linker
20-
This topic describes Unicode support in the Visual C++ build tools.
21-
22-
Filenames
23-
Filenames specified on the command line or in compiler directives (such as #include) may now contain Unicode characters.
24-
25-
Source code files
26-
Unicode characters are now supported in identifiers, macros, string and character literals, and in comments. Universal character names are also now supported.
27-
28-
Unicode can be input into a source code file in the following encodings:
29-
30-
- UTF-16 little endian with or without byte order mark (BOM)
31-
32-
- UTF-16 big endian with or without BOM
33-
34-
- UTF-8 with BOM
35-
36-
Output
37-
During compilation, compiler outputs diagnostics to the console in UTF-16. The characters that can be displayed at your console depend on the console window properties. Compiler output redirected to a file is in the current ANSI console codepage.
38-
39-
Linker response files and .DEF files
40-
Response files and DEF files can be either UTF-16 with a Byte Order Mark or ANSI. Previously only ANSI was supported.
41-
42-
.asm and .cod dumps
43-
.asm and .cod dumps are in ANSI by default for compatibility with MASM. Use /FAu to output UTF-8. Note that if you specify /FAs, the intermingled source will just be directly printed and may look garbled, for example if source code is UTF-8 and you didn't specify /FAsu.
44-
45-
You can enable Unicode file names in the development environment (see [Working with Project Properties](../../ide/working-with-project-properties.md)) by selecting the appropriate tool and by selecting the **Enable Unicode Response Files** property, which is enabled by default. One reason you might change this default is if you modify your development environment to use a compiler that does not have Unicode support.
46-
47-
## See Also
48-
[Build C/C++ code on the command line](../../build/building-on-the-command-line.md)
16+
17+
Most Visual C++ build tools support Unicode inputs and outputs.
18+
19+
## Filenames
20+
21+
Filenames specified on the command line or in compiler directives (such as `#include`) may contain Unicode characters.
22+
23+
## Source code files
24+
25+
Unicode characters are supported in identifiers, macros, string and character literals, and in comments. Universal character names are also supported.
26+
27+
Unicode can be input into a source code file in the following encodings:
28+
29+
- UTF-16 little endian with or without byte order mark (BOM)
30+
31+
- UTF-16 big endian with or without BOM
32+
33+
- UTF-8 with BOM
34+
35+
## Output
36+
37+
During compilation, the compiler outputs diagnostics to the console in UTF-16. The characters that can be displayed at your console depend on the console window properties. Compiler output redirected to a file is in the current ANSI console codepage.
38+
39+
## Linker response files and .DEF files
40+
41+
Response files and DEF files can be either UTF-16 with a BOM, or ANSI.
42+
43+
## .asm and .cod dumps
44+
45+
.asm and .cod dumps are in ANSI by default for compatibility with MASM. Use [/FAu](../../build/reference/fa-fa-listing-file.md) to output UTF-8. Note that if you specify **/FAs**, the intermingled source will just be directly printed and may look garbled, for example if source code is UTF-8 and you didn't specify **/FAsu**.
46+
47+
## See also
48+
49+
[Build C/C++ code on the command line](../../build/building-on-the-command-line.md)

0 commit comments

Comments
 (0)