Skip to content

Commit df7a75f

Browse files
committed
fix 'chance' to 'change' per alankilborn
1 parent 35d5056 commit df7a75f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/docs/encoding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ If you find that your text with accented characters often gets misinterpreted by
3939

4040
As of Notepad++ version 8.8.8, the **ANSI** and **Convert to ANSI** entries on the **Encoding** menu are disabled when the Windows setting **Use Unicode UTF-8 for worldwide language support** is enabled. When that setting is in effect, the system default code page, which ordinarily defines “ANSI” in Windows, *is* UTF-8; attempting to treat UTF-8 as an ordinary code page does not work properly, which caused erratic behavior prior to version 8.8.8. Since the traditional concept of “ANSI” has no consistent meaning when that Windows setting is enabled, Notepad++ disables `ANSI` encoding. (But even with that OS option set, Notepad++ can still choose one of the Character Set encodings; it just manually selects that entry, not setting it to "ANSI".)
4141

42-
Some Windows 11 installations are coming with that option turned on by default. If you need to be able to use the **Convert to ANSI** action, and you find it's disabled in Notepad++ v8.8.8 or newer (or if that conversion doesn't behave as expected on older versions of Notepad++), you can verify in **?**-menu's **Debug Info**: it will show `Current ANSI codepage: 65001` if that Windows OS option is on. If you want to chance that Windows OS setting, Microsoft provides multiple paths to that setting, but two of the common ways to find it are:
42+
Some Windows 11 installations are coming with that option turned on by default. If you need to be able to use the **Convert to ANSI** action, and you find it's disabled in Notepad++ v8.8.8 or newer (or if that conversion doesn't behave as expected on older versions of Notepad++), you can verify in **?**-menu's **Debug Info**: it will show `Current ANSI codepage: 65001` if that Windows OS option is on. If you want to change that Windows OS setting, Microsoft provides multiple paths to that setting, but two of the common ways to find it are:
4343
1. Windows **Control Panel > Clock & Region** (or just **Region**), go to the **Administrative** tab on the dialog, using the **Change System Locale** button, and toggle the **Use Unicode UTF-8 for worldwide language support** checkmark.
4444
2. Windows **Settings > Time & Language**, in the **Language** (or **Language & Region**) section, find the **Use Unicode UTF-8 for worldwide language support** toggle (it may be not show, in which case, look under the **Windows Display Language** ▼ pulldown to show it).
4545

0 commit comments

Comments
 (0)