Encoding
To display and edit files correctly, CLion needs to know which encoding to use. In general, source code files are mostly in UTF-8. This is the recommended encoding unless you have some other requirements.
To determine the encoding of a file, CLion uses the following steps:
If the byte order mark (BOM) is present, CLion will use the corresponding Unicode encoding regardless of all other settings. For more information, see Byte order mark.
If the file declares the encoding explicitly, CLion will use the specified encoding. For example, this can apply to XML, HTML, and JSP files. The explicit declaration also overrides all other settings, but you can change it in the editor.
If there is no BOM and no explicit encoding declaration in the file, CLion will use the encoding configured for the file or directory in the file encoding settings. If encoding is not configured for the file or directory, CLion will use the encoding of the parent directory. If the parent directory encoding is also not configured, CLion will fall back to the Project Encoding, and if there is no project, to Global Encoding.
Change the encoding used to view a file
If CLion displays characters in a file incorrectly, it probably couldn't detect the file encoding. In this case, you need to specify the correct encoding to use for viewing and editing this file.
With the file open in the editor, either select from the main menu or click the File Encoding widget on the status bar, and select the correct encoding of the file.
Encodings marked with
or 
might change the file contents. In this case, CLion opens a dialog where you can choose what to do with the file:Reload: load the file in the editor from disk and apply encoding changes to the editor only. You will see the content changes related to the chosen encoding, but the actual file will not change.
Convert: overwrite the file with the chosen encoding.
This will add an association for the file to the file encoding settings. CLion will use the specified encoding to view and edit this file.
Configure file encoding settings
In the Settings/Preferences dialog (Ctrl+Alt+S) , select .
CLion uses these settings to view and edit files for which it was not able to detect the encoding and also uses the specified encodings for new files.
Global Encoding | Select the encoding to use when other encoding options don't apply. For example, CLion will use this encoding for files that are not part of any project or when you check out sources from a version control system. |
Project Encoding | Select the encoding to use for files that are not listed in the table. |
Path | Specify the path to the files or directories for which you want to configure the encoding. |
Encoding | Select the encoding to use for the specified files and directories. If this selector is disabled, the file probably has a BOM or declares the encoding explicitly. In this case, you can't configure the encoding to use for this file. The encoding selected for a directory applies to all files and subdirectories within it. |
Default encoding for properties files | Select the encoding for properties files in your project. |
Transparent native-to-ascii conversion | Show national characters (those not defined in ISO 8859-1) in place of the corresponding escape sequences. |
Create UTF-8 files | Select how CLion should create UTF-8 files:
By default, CLion creates UTF-8 files without the BOM because some software is not compatible with the BOM, and it may be a problem when interpreting scripts. However, in some cases, you may want to have the BOM in your UTF-8 files. |
Select console output encoding
By default, CLion uses the system encoding to view console output.
In the Settings/Preferences dialog (Ctrl+Alt+S) , select .
Select the default encoding from the Default Encoding list.
Click OK to apply the changes.