Update compatibility info on readme

This commit is contained in:
Isaiah Odhner 2023-08-31 23:09:28 -04:00
parent c063b92c2f
commit 50778b4f1b

View File

@ -211,10 +211,14 @@ Python 3.10 or later is required.
### Linux
Tested on Ubuntu 22, with GNOME Terminal, and VS Code's integrated terminal.
Tested on Ubuntu 22, with GNOME Terminal, Kitty, XTerm, and VS Code's integrated terminal.
GNOME Terminal works best, with crisp triangles used for icons in dialogs, emoji support, and true color support.
Kitty works fine, supporting true color and emoji.
XTerm supports true color, but not emoji. Run with `TERM=xterm-256color textual-paint --ascii-only` for XTerm compatibility.
### macOS
Tested on OSX 10.14 (Mojave), with iTerm2, and VS Code's integrated terminal.
@ -258,6 +262,8 @@ If this happens, I would recommend first messing around with it, since it's a fu
Textual Paint will **not** work properly with the old Windows console (`conhost.exe`), which lacks emoji/Unicode support and true color support.
This program is commonly thought of as the "Command Prompt", but the Command Prompt (`cmd.exe`) is actually a *shell* (like `bash`) that can run in either the old console or the new Windows Terminal, which are both *terminal emulators*.
You can run with `--ascii-only` to limit the characters used in the UI to ASCII, but colors will still be limited and similar colors will appear confusingly identical.
### VS Code
Note that VS Code's integrated terminal tries to fix the contrast of text, including in the canvas, which is entirely inappropriate for an ANSI art editor, as it obscures the colors, and can indeed *harm* the contrast of the resulting document, by tricking you into thinking there's more contrast than there actually is.