Windows 11 – Counterclockwise Arrows Emoji Displays Incorrectly

Problem is that coding Latin-2 (iso-8859-2) and Windows-1250 (used by windows) differ in some characters:

ž, š, ť, Ž, Š, Ť

All differences are summarized at Wikipedia or Czech version

If you set encoding=cp1250, then it'll be ok.

I don't want to prolong comments so I'm adding that here.

There is a problem that standard code page uses only 1byte (hex 100) for characters, so there are ISO standards for different languages. If you have set encoding iso-8859-2 and trying to add unicode character (hex 160) Š, than gvim loops over to character (hex 60). You have to use codes ISO-8859-2, where Š ìs (hex 089). Other codes here: http://cs.wikipedia.org/wiki/ISO_8859-2

UTF-8 on the other hand uses 2bytes and contains simultaineously all? letters and signs. So if you use set encoding=utf-8 and then add U0160 or U5927 you'll get Š resp. 大.

Fixedsys contains ů and Ů, OR there is a difference in font versions between Windows language mutations (I use Czech version), but I doubt that. You can use windows utility Charmap.exe, there you can select desired font and check which characters it supports, even their unicode code.

I was trying briefly some of default fonts in GVim and there seems to be some that supports Chinese (ie MS Mincho), but I don't which signs are important.

GVim seems to be supporting only monospace character fonts so, if you'll be searching for another font be aware of that. :)

You need proper Unicode all the way up the stack from OS-Locale, to Terminal, to Tmux, to Vim. Each part of the chain must support Unicode properly.

For your OS-Locale

you need something like: set LANG="en_US.UTF-8"

For Tmux

Try starting tmux using tmux -u, like Jon suggested. If that doesn't work then you might need to check your config files .tmux.conf or reset to default.

FOR VIM

You need to compile vim with multi-byte support.

The easiest way to do this is to run

./configure --with-features=big
make

This will build vim with the correct support.

You can verify that it was compiled correctly with

:version

in vim or by running

vim --version

and looking for +multi_byte. If it says -multi_byte it will not work.