Bug 816658 - xemacs warning: Missing charsets in String to FontSet conversion
xemacs warning: Missing charsets in String to FontSet conversion
Product: Fedora
Classification: Fedora
Component: xemacs (Show other bugs)
All Linux
unspecified Severity low
: ---
: ---
Assigned To: Jerry James
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-26 11:46 EDT by J
Modified: 2012-04-26 12:11 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-04-26 12:11:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description J 2012-04-26 11:46:24 EDT
Description of problem:
when starting xemacs from the command line it gives the warning "Missing charsets in String to FontSet conversion"

Version-Release number of selected component (if applicable):
Fedora 16

How reproducible:
every time

Steps to Reproduce:
1. open terminal
2. type xemacs
3. there's the warning
Actual results:
the warning is given

Expected results:
there shouldn't be a warning

Additional info:
The problem can be solved by installing the terminus-fonts package.  Perhaps the rpm should add a depencency requirement for that package.
Comment 1 Jerry James 2012-04-26 12:11:27 EDT
This is not an XEmacs bug.  Please see bug 478370, especially comments 13 and 17.  The bug is that Fedora ships a libX11-common package with an XLC_LOCALE file for en_US.UTF-8 that requires ISO8859-13, but there are no xorg-x11-fonts-ISO8859-13-* packages.  This is a generic X11 bug, not specific to XEmacs.

The XEmacs package doesn't requires terminus-fonts; it works fine for most users without that package installed, so adding the suggested Requires is wrong.  Feel free to file a bug against the libX11 package if the warning message bothers you.  I personally think that the ISO8859-13 requirement should be removed from the en_US.UTF-8 locale, but what do I know?

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