How can I make my terminal display this character correctly?

[cracauer@]

After "short". This is a dash, but not the 7-bit minus sign. Hex code is E2.

The fault is not in my terminal or my font, the same display shows up in xterm and kitty.

 

[bakul]

Does "export LANG=en_US.UTF-8" or equivalent for UTF8 for your country help? If that doesn't help show us $TERM and output of "stty all".

 

[T-Aoki]

No.
It's NOT single byte 0xE2, but a part of 3bytes UTF-8.
Opening the attached file in leafpad, select the offending character and pasting it into search window of gucharmap states

U+2014 EM DASH
UTF-8: 0xE2 0x80 0x94
UTF-16: 0x2014

So, is your terminal(s) configured for UTF-8 and having multibytes capable fonts? Screenshot of Kitty is like below for me. LANG=ja_JP.UTF-8 and I have (had) set dspmbyte=utf8 when I was mainly using tcsh (not all shells would need such an configuration, though).

For vty, there's b16.fnt provided by Ed Maste that covers this character.

 

[Charlie_]

In such cases, you can also use Emacs (provided the font is installed).
env LANG=C.UTF-8 emacs -e term

 

[T-Daemon]

It must be the environment of the logged-in user responsible for not showing the character in question.

A new created, un-customized user account (on 15.1) shows the character ("short**—the") correctly, in console (default console font "terminus").

Also correctly in xterm and kitty (no custom font set). On your system might be a compatible font package missing [1].

 $ env
LANG=C.UTF-8
SHELL=/bin/sh
TERM=xterm
XTERM_LOCALE=C.UTF-8
XTERM_SHELL=/bin/sh
XTERM_VERSION=XTerm(411)

[1]

 $ kitty --debug-font-fallback=yes
[0.194] Text fonts:
[0.194]   Normal: NotoSansMono-Regular: /usr/local/share/fonts/noto/NotoSansMono-Regular.ttf:0
Features: ()
[0.195]   Bold: NotoSansMono-Bold: /usr/local/share/fonts/noto/NotoSansMono-Bold.ttf:0
Features: ()
[0.195]   Italic: NotoSansMono-Regular: /usr/local/share/fonts/noto/NotoSansMono-Regular.ttf:0
Features: ()
[0.195]   Bold-Italic: NotoSansMono-Bold: /usr/local/share/fonts/noto/NotoSansMono-Bold.ttf:0

 

[T-Aoki]

(provided the font is installed)

Yes. As EM DASH (U+2014 in Unicode code point) is mapped to 3bytes region of UTF-8 (0xE2 0x80 0x94), not all non-CJK fonts would have its gryph.

And basically unrelated with anyone who doesn't read/write Japanese, but EM DASH has compatibility issue between CP932 (IBM, old MS) and Unicode, due to mis-print in first print of JIS X 0213:2000 standard sheet (code point of Unicode for full width dash [全角ダッシュ], which is 0x815C in Shift-JIS, as U+2015 and it is corrected as U+2014 in later prints).
CP932 (Shift-JIS for IBM/earlier MS) maps to U+2015 while Apple (and later MS) maps correct U+2014, thus, conversion error could happen.
So Japanese writers who are aware of this issue avoid using EM DASH whenever possible / allowed.
This issue is described in Japanese version of Wikipedia, but not in English version.

 

[cracauer@]

Yeez. I'll go through this later.