Different types of files use different ways to define encoding. JetBrains DataSpell recognizes encoding of files based on their contents.
Encoding has influence on the way JetBrains DataSpell reads or writes files. If a file has been modified but not yet saved, any changes in encoding affect file writing; if a file has not been modified, then reading is affected. JetBrains DataSpell suggests specific ways to change encoding of a file according to its type, using File Encodings Settings page, the Status bar, or the editor.
|Encoding||Can be changed in|
|File encoding is specified within the file, for example, in XML.||If a file contains explicit encoding declaration, you can change it in the Editor. In this case JetBrains DataSpell provides code completion.|
|File encoding is defined by BOM||In this case, you can't change encoding with which JetBrains DataSpell reads the file, but it is still possible to change encoding for writing such file.|
|UTF characters are detected in the file contents.||JetBrains DataSpell provides an option that automatically changes file encoding to UTF, if the file contents can be reasonably interpreted as UTF. |
This option only works for reading; a file can be saved with any encoding.
|Encoding cannot be found out from the file contents.||In this case, the default encoding is the one defined by the IDE encoding in the File Encodings page of the Settings dialog. You can change it for multiple files and directories, or for a single file.|