File Encodings
If the file or directory encodings are not defined, then the project encoding is used. In case the project encoding cannot be taken (for example, when the project is not yet created), DataSpell uses global encoding.
File or directory encodings take precedence over the project encoding, which, in turn, takes precedence over the global encoding.
Global Encoding | Select the encoding to use when other encoding options don't apply. For example, DataSpell 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 DataSpell should create UTF-8 files:
By default, DataSpell 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. |