Skip to content

Commit 512caab

Browse files
author
Colin Robertson
committed
Update to address 3019
1 parent c5e1faa commit 512caab

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

docs/build/reference/unicode-support-in-the-compiler-and-linker.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
description: "Learn more about: Unicode Support in the Compiler and Linker"
2+
description: "Learn more about: Unicode support in the compiler and linker"
33
title: "Unicode Support in the Compiler and Linker"
4-
ms.date: "12/15/2017"
4+
ms.date: 03/07/2021
55
f1_keywords: ["VC.Project.VCLinkerTool.UseUnicodeResponseFiles", "VC.Project.VCLibrarianTool.UseUnicodeResponseFiles", "VC.Project.VCCLCompilerTool.UseUnicodeResponseFiles", "VC.Project.VCXDCMakeTool.UseUnicodeResponseFiles"]
66
helpviewer_keywords: ["Unicode, Visual C++"]
77
---
8-
# Unicode Support in the Compiler and Linker
8+
# Unicode support in the compiler and linker
99

10-
Most Visual C++ build tools support Unicode inputs and outputs.
10+
Most Microsoft C/C++ (MSVC) build tools support Unicode inputs and outputs.
1111

1212
## Filenames
1313

@@ -25,17 +25,21 @@ Unicode can be input into a source code file in the following encodings:
2525

2626
- UTF-8 with BOM
2727

28+
In the Visual Studio IDE, you can save files in several encoding formats, including Unicode ones. Save them in the **Save File As** dialog by using the dropdown on the **Save** button. Select **Save with Encoding** in the dropdown. Then, in the **Advanced Save Options** dialog, select an encoding from the dropdown list. Choose **OK** to save the file.
29+
2830
## Output
2931

3032
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.
3133

32-
## Linker response files and .DEF files
34+
## Linker response files and `.DEF` files
35+
36+
Response files and *`.DEF`* files can be either UTF-16 or UTF-8 with a BOM, or ANSI.
3337

34-
Response files and DEF files can be either UTF-16 with a BOM, or ANSI.
38+
## `.asm` and `.cod` dumps
3539

36-
## .asm and .cod dumps
40+
*`.asm`* and *`.cod`* dumps are in ANSI by default for compatibility with MASM. Use [`/FAu`](fa-fa-listing-file.md) to output UTF-8.
3741

38-
.asm and .cod dumps are in ANSI by default for compatibility with MASM. Use [/FAu](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**.
42+
If you specify **`/FAs`**, the intermingled source gets printed directly. It may look garbled, for example, when the source code is UTF-8 and you didn't specify **`/FAsu`**.
3943

4044
## See also
4145

0 commit comments

Comments
 (0)