From e19ddd5721b8809e1167d765e9f76ca7d1e091f7 Mon Sep 17 00:00:00 2001 From: burner1024 Date: Sun, 21 May 2023 17:29:10 +0700 Subject: [PATCH] Update README.md typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d300af8..3cfa446 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ jobs: 1. Less options. In particular, there's no (no)convert/(no)reload arrays. Use `WITH_TRA`/`LOAD_TRA`/`USING` to scope your tra files to corresponding components. 2. Any file named `ee.tra` or matching `*_ee.tra` mask is inferred to be in UTF-8, even if the rest of the files are in Windows-specific encoding. -3. Files named `setup.tra` or `install.tra` are inferred to be in Windows-specific encoding, even the rest of the files are in UTF-8. +3. Files named `setup.tra` or `install.tra` are inferred to be in Windows-specific encoding, even if the rest of the files are in UTF-8. 4. Files named `setup.tra` or `install.tra` in Russian or Ukrainian languages are inferred to be in `cp866` encoding, not `cp1251`. That's the correct console encoding in Windows in those languages. 5. In Linux and Mac OS, usual console encoding is UTF-8. `split_console` allows you to generate multiple OS-specific console message files with correct encoding. One `setup.tra` turns into 3 files: `setup-win32.tra`, `setup-unix.tra`, `setup-osx.tra`. Same goes for `install.tra`.