![]() In this case, you need to specify the correct encoding to use for viewing and editing this file. If CLion displays characters in a file incorrectly, it probably couldn't detect the file encoding. 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. If encoding is not configured for the file or directory, CLion will use the encoding of the parent directory. 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. ![]() The explicit declaration also overrides all other settings, but you can change it in the editor. For example, this can apply to XML, HTML, and JSP files. If the file declares the encoding explicitly, CLion will use the specified encoding. For more information, see Byte order mark. If the byte order mark (BOM) is present, CLion will use the corresponding Unicode encoding regardless of all other settings. To determine the encoding of a file, CLion uses the following steps: This is the recommended encoding unless you have some other requirements. In general, source code files are mostly in UTF-8. To display and edit files correctly, CLion needs to know which encoding to use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |