![]() ![]() If the locale does not use UTF-8 encoding, you are able to change these menu entries and see the resulting differences. If your locale uses UTF-8 encoding (and if the locale resource uses the default value), then xterm pre-selects these menu items and disables them from being changed. ![]() Xterm has menu items for UTF-8 Encoding and UTF-8 Fonts. The uxterm script selects the latter at startup using the -class option, but as described in the manual page, xterm will automatically select the utf8Fonts at startup based on the locale settings. There is more than one app-defaults file because that seemed a simpler solution than the utf8Fonts arrangement. But they have only 192 characters (256 - 64 control characters), while the bitmap UTF-8 fonts have thousands. Those short names are (as detailed in xterm cannot load font) aliases for ISO-8859-1 fonts, which (unsuprisingly given the history of UTF-8) have the same appearance as the UTF-8 fonts. Just reading the XTerm app-defaults file, most users would not notice that the non-UTF-8 fonts given here look something like the UTF-8 fonts: *VT100.font1: nil2 Here is the content from the XTerm app-defaults file: *2: -misc-fixed-medium-r-normal-8-80-75-75-c-50-iso10646-1 The app-defaults files XTerm and UXTerm have both of these, but in the latter, those Unicode fonts are not inside the utf8Fonts layer. utf8Fonts.font, etc., are Unicode fonts., font6 are the conventional fonts dating back to X11R4. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |