8 Mar
2016
8 Mar
'16
2:49 a.m.
I had the same issue in xterm. Changing fonts didn't fix it, but switching to urxvt (with the same font) did. It seems like there's something screwy with xterm's unicode support. On Mon, Mar 7, 2016 at 12:12 AM, Grady Martin <sunnycemetery@gmail.com> wrote:
On 2016年02月17日 00時06分, Garmine 42 wrote:
It was indeed a font issue, the one I used did not contain the braille characters. Because the same problem existed on my gettys I thought it was an encoding issue or something else. Using terminus font at the moment (as suggested) and it works perfectly fine.
Well, I am glad I was not the only one affected by this. I wish there were at least an option to decide which characters get displayed.