However, we did not see anything informative there, nor did we find anything useful by running dmesg. The first thing we did was to take a look at the logs ( /var/log). He tried running term in numerous ways ( CTRL-SHIFT-T e.g.), and again, nothing happened.įortunately, xterm could start, so we had a toehold. He tried to run term from the menu, and nothing happened. He uses linux mint (I use Ubuntu, and I don’t know if the same problem occurs in Ubuntu). Depending on your fontconfig arrangement, you can get a workable coverage from the TrueType fonts (with the caveat that some of those are sized incorrectly).A friend of mine just experienced a very strange issue. In xterm, it is treated as a nuisance (see menuLocale resource).īesides bitmap-fonts, xterm also supports TrueType fonts, and will automatically lookup fonts as needed to fill in for missing glyphs from the family specified with the -fa option. There is a font-set feature in the X libraries, but it has severe performance problems and was never widely used. Xterm uses only one of these bitmap-fonts at a time (along with automatically using bold- and italic-versions). Xresources so that if the default one doesn't have some unicode characters, the additional one can display them? While one could make font sets using bitmap fonts, which would allow one to do what's asked in the question:Ĭan I have an additional font in my. You can specify in your X resources which file to use by prefixing the resources with XTerm or UXTerm, respectively. 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.
#Uxterm tried to use locale manual#
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.
![uxterm tried to use locale uxterm tried to use locale](https://i.stack.imgur.com/uYoEi.png)
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.
![uxterm tried to use locale uxterm tried to use locale](https://www.trendsmap.com/ipx/https://pbs.twimg.com/ext_tw_video_thumb/1561349769506717698/pu/img/r8k7LKrN_-xASr9k.jpg)
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.
![uxterm tried to use locale uxterm tried to use locale](https://france.detailzero.com/temp/resized/medium_2022-08-18-1fec7f3642.jpg)
utf8Fonts.font, etc., are Unicode fonts.
![uxterm tried to use locale uxterm tried to use locale](https://eatwithme.net/wp-content/uploads/2022/08/Untitled1-1-850x491.png)
, font6 are the conventional fonts dating back to X11R4.