Use this settings page to configure encoding options globally, for the current project, or for any file or directory in your project.
If the file or directory encodings are not defined, then the project encoding is used. If the project encoding cannot be taken (for example, if a project is not yet created), then the global encoding is used.
From this drop-down list, choose the encoding that should be used by default if no other encoding options are specified. The encoding will be applied, for example, when you specify settings of a default project or check out sources from a version control storage. Choose System Default to have the default encoding of your operating system used or choose a specific encoding.
From this drop-down box, choose the default encoding to use in the folders for which no encoding is appointed in the Default encoding field below. Choose System Default to have the default encoding of your operating system used or choose a specific encoding.
This column displays the project tree view.
|This column displays encoding for a file or directory, if applicable. If encoding is defined within a file, it cannot be configured, and is shown in grey font. If encoding is configurable, click the Default Encoding column for a selected file or directory, and choose encoding from the drop-down list. |
Encoding information embedded in a file overrides the selected one; encoding information for the nested files or directories overrides that for the outer directories or the whole project.
Default encoding for properties files
Use this drop-down list to define encoding for the properties files in the project.
Transparent native-to-ascii conversion
Select this option to show in properties files the national characters (non-ISO 8859-1), stored as escape sequences. If this checkbox is not selected, the national characters will not be shown.
Create UTF-8 files
Use this selector to choose how CLion should create UTF-8 files: with byte order mark (BOM), without BOM, or BOM only for Windows. It might be helpful if you are working with the OS other than Windows and want more flexibility for the UTF-8 file encoding. Keep in mind that the UTF-8 with BOM option may cause problems with software which is not compatible with BOM or with scripts that need to be run by an interpreter.