To display and edit files correctly, AppCode 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, AppCode uses the following steps:
If the byte order mark (BOM) is present, AppCode 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, AppCode will use the specified encoding. For example, this can apply to XML or HTML 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, AppCode 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, AppCode will use the encoding of the parent directory. If the parent directory encoding is also not configured, AppCode 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 AppCode 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 File Encoding widget on the status bar, and select the correct encoding of the file.from the main menu or click the
Encodings marked with or might change the file contents. In this case, AppCode 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. AppCode will use the specified encoding to view and edit this file.
Configure file encoding settings
Press ⌃ ⌥ S to open the IDE settings and select.
AppCode uses these settings to view and edit files for which it was unable to detect the encoding and uses the specified encodings for new files. For more information, see File Encodings.
Select console output encoding
By default, AppCode uses the system encoding to view console output.
In the Preferences dialog (⌃ ⌥ S), select .
Select the default encoding from the Default Encoding list.
Click OK to apply the changes.
For more information about console output settings, see Console.
Different types of files use different ways to define encoding. AppCode recognizes encoding of files based on their contents.
Encoding has influence on the way AppCode 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. AppCode suggests specific ways to change encoding of a file according to its type, using File Encodings Settings page, the Status bar, or the editor.
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 AppCode provides code completion.
File encoding is defined by BOM
In this case, you can't change encoding with which AppCode reads the file, but it is still possible to change encoding for writing such file.
UTF characters are detected in the file contents.
AppCode 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.