![]() ![]() The locale in effect when you start xterm affects how it interprets the same codes. UTF-8 encoding uses codes in the 0x80-0xff range to build up multi-byte characters, which is not what you want. That tells applications running inside xterm to use UTF-8. Your shell's locale settings are part of the problem: I'd be grateful for any help, and happy to provide any and all detail. Restoring that glyph is what put me on this chase. That character appeared fine running under Sun Solaris, but displays a blank in kubuntu linux with ncurses. We have a custom program that invokes an xterm-based editor, using curses tools, which displays at least one character in the 128-255 range. I'm running 32-bit kubuntu, rather than 64-bit. Plenty of other people have written to the forums with similar problems, and they were solved by adjustments as in the above list. In all cases, only the default '?' glyphs are displayed. In addition to the simple echo -e test, used test programs thatĭisplay full font grids or invoke appropriate vt-100 esc-commandĮscape ( '<' (to load the DEC Supplemental Character Set into G1)Ĭtrl-N (shift-out, to load G1 into the "left-half" GL set) Start xterm with different fonts invoked, all of which have the full I've tried a selection of characters above 128 (= 0x80), same result for all. These are characters 162 & 163(decimal) and in western fonts should display as cent sign and British pound. ![]() When I try, depending on the settings, I get either a blank or the default glyph of question mark in a dark oval. All characters in range 0x20-0x7e display as expected, but none in range 0x80-0xfe. I have tried every method I could find in the forums, and cannot display any 8-bit character in an xterm window, under kubuntu 18.04 (nor in earlier versions).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |