![]() However, you can solve your problem with cpp using include files. In particular, you can't have a line break in the expansion of a cpp macro, so you can't define a macro to expand to multiple X resources. Unfortunately, cpp is not very convenient for the X resource syntax. xrdb (the utility that loads X resources) uses the C preprocessor ( cpp) by default. The solution is to rely on the preprocessor. *XTerm means “ XTerm at any level of the hierarchy”, not “any name that ends with XTerm”. Wildcards match components, not individual characters inside components. In general, you can't do this with the basic X resource syntax alone. In this specific case, you could perhaps use ?.VT100.background: Blackīecause in practice, xterm is the only application with a VT100 widget. You can get two tiers of configuration this way, but if you want three tiers, this won't help. With these definitions, xterm -name light has a white background and has scroll bars. It can manage bitmap fonts, but the available information suggests that it will attempt to scale those, making the result worse than just selecting bitmap fonts directly.If you want to have multiple XTerm configurations and choose one at invocation time, you can use a single class and multiple instance names: : Black That's what fontconfig attempts to do (not always successfully). The reason why there is no font-set support for bitmap fonts is that someone would have to manage the data to show which fonts are compatible and would be suitable. Here's a screenshot of Arabic using the ncurses test-program (page at U+0600): Since late 2018, xterm provides font-set support for TrueType fonts you would need xterm patch #338 or later, e.g.,.Since font-set support by the X libraries used by xterm is less than adequate (see FAQ regarding Xaw's use of the feature), that means xterm would have to provide its own implementation of font-sets.The existing bitmap fonts with good coverage are for small fontsizes (and perhaps not good enough).To get "good" coverage of the Arabic, etc., would either take a large font or font-set support: The resources indicated in the question are for bitmap fonts. Xterm (uxterm is a script) uses either bitmap fonts or TrueType fonts. I think I read somewhere that (u)xterm is supposed to use a default font and then if it needs to display some glyph or character that isn't in that font, it falls to a second choice. I am also very fond of xterm's default font for English characters and I'd like to keep that. The issue is that I can't figure out a font which can display both Arabic, English and the rest of the unicode like the original fixed font did. This worked and I got some Arabic to be displayed in uxterm. I suspected the font being used by uxterm didn't have the Arabic glyphs However, if I try any other unicode text, uxterm is able to display it normally. I need to be able to deal with Arabic file names and directories from terminal and I'd like to achieve that with xterm but instead of displaying Arabic characters it shows dotted rectangles (whether I type them in the prompt or they are being output).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |