Bug 454232 - xterm should require xorg-x11-fonts-misc
xterm should require xorg-x11-fonts-misc
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: comps (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Bill Nottingham
Jeremy Katz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-06 23:34 EDT by Jens Petersen
Modified: 2014-03-16 23:15 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-10 19:22:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jens Petersen 2008-07-06 23:34:27 EDT
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.
Comment 1 Miroslav Lichvar 2008-07-08 11:35:04 EDT
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?
Comment 2 Bill Nottingham 2008-07-08 14:06:01 EDT
*cough* Use a terminal that supports a real font library.
Comment 3 Bill Nottingham 2008-07-08 14:07:08 EDT
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.
Comment 4 Jens Petersen 2008-07-08 19:39:28 EDT
(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".
Comment 5 Jens Petersen 2008-07-08 19:44:36 EDT
(It also purports to support Indic and Arabic...)

Or maybe we just need the GNU unifont.  Well there are various options. :)
Comment 6 Tony Fu 2008-09-09 23:09:37 EDT
requested by Jens Petersen (#27995)
Comment 7 Bill Nottingham 2008-09-10 19:22:31 EDT
Made optional.

Note You need to log in before you can comment on or make changes to this bug.