On Tue, Mar 8, 2016 at 3:57 AM, Garmine 42 <mikro001@xxxxxxxxx> wrote: > > On 8 March 2016 at 03:49, Maxwell Anselm <silverhammermba@xxxxxxxxx> wrote: > > 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@xxxxxxxxx> > > 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. > >> > > You need to enable unicode in xterm - i.e. use uxterm instead of xterm. I already have unicode enabled in xterm. And Braille does show up if I switch to the default bitmap font, but for whatever reason it doesn't show up when I use Dejavu Sans Mono (which I prefer). urxvt has no such problem.
