Description of problem: Since we no longer install xorg-x11-fonts-* by default xterm does have much coverage of non-ascii now. I suggest making it require xorg-x11-fonts-misc which should help with that. Steps to Reproduce: 1. run xterm on Japanese desktop 2. run "date" in xterm shell Actual results: 1. warning appears: "Warning: Cannot convert string \"nil2\" to type FontStruct" 2. empty spaces in place of Japanese characters in date Expected results: 1. no warning 2. Japanese date to be displayed Additional info: Installing xorg-x11-fonts-misc solves the above problems.
I'm not sure that adding to xterm a dependency on a particular font is a good idea. Maybe it would be better to add it to the Japanese support (and other supported languages) in comps?
*cough* Use a terminal that supports a real font library.
Because, even if we add a requirement for -misc, that might catch some japanese, but what about chinese? Thai? Arabic? etc. We don't add requirements for fontconfig-using apps on specific language fonts, so I'm not sure why xterm would require one.
(In reply to comment #3) > Because, even if we add a requirement for -misc, that might catch some japanese, > but what about chinese? Thai? Arabic? etc. Shrug, it would at least cover CJK. > We don't add requirements for fontconfig-using apps on specific language fonts, > so I'm not sure why xterm would require one. True. We used to install xorg-x11-fonts-misc by default... (In reply to comment #2) > *cough* Use a terminal that supports a real font library. Maybe the question then is why are we installing xterm by default. Shall I make it optional in comps? Maybe that makes more sense: though sometimes it is handy to have xterm around for "emergencies".
(It also purports to support Indic and Arabic...) Or maybe we just need the GNU unifont. Well there are various options. :)
requested by Jens Petersen (#27995)
Made optional.