Text encodings and line endings

Last updated Screenshots show Folora 0.2.0.

Folora detects the encoding when it opens a file and saves in the original encoding. It does not convert files to UTF-8.

Encodings that can be opened

  • UTF-8, with or without a BOM.
  • UTF-16, detected with or without a BOM.
  • Other common legacy encodings, such as Big5, GB18030 (including GBK), Shift_JIS, EUC-KR and Windows-1252.

A file in which no text encoding can be detected is treated as a non-text file, and Folora shows “… is not a text file, so it cannot be opened.”

Saving

  • If you save a file without editing it after opening, the file’s bytes and modification time stay unchanged.
  • If the document contains a character the original encoding cannot represent, such as an emoji typed into a Big5 file, saving stops and Folora shows “This file is saved in Big5, which has no place for” followed by the character. Delete that character and save again.
  • Copies recovered from the recovery log keep the original encoding and line endings.

Line endings

  • LF and CRLF are both supported, and saving keeps the file’s original line endings.
  • When you edit and save a file that mixes LF and CRLF, all line endings become CRLF.
  • Files that use CR alone for line endings are not supported; CR characters in a file are kept as they are.

FOLORA