Bug 107120 - xemacs get weird fonts when running with UTF-8
Summary: xemacs get weird fonts when running with UTF-8
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xemacs
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-15 07:44 UTC by David Juran
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-10-16 16:13:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
screenshot of emacs with those weird fonts in the menus (67.28 KB, image/jpeg)
2003-10-15 07:48 UTC, David Juran 		no flags Details
View All

Description David Juran 2003-10-15 07:44:32 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031009

Description of problem:
When starting xemacs in a UTF-8 locale, it first spews out "Warning: Missing
charsets in String to FontSet conversion" twice on std. err. and then when when
it starts the fonts in the menus looks weird.

Version-Release number of selected component (if applicable):
xemacs-21.4.14-1

How reproducible:
Always

Steps to Reproduce:
1.export LANG=en_US.UTF-8
2.xemacs
Comment 1 David Juran 2003-10-15 07:48:31 UTC 
Created attachment 95189 [details]
screenshot of emacs with those weird fonts in the menus
Comment 2 Jens Petersen 2003-10-15 11:44:22 UTC 
I'm not able to reproduce this with a fresh FC test3 install.

Can you give more details?
Are you running an upgrade from RHL or something?
Comment 3 David Juran 2003-10-15 16:51:38 UTC 
This machine was freshly installed with FC test2 and then upgraded (using the
upgrade option on the test 3 cd:s) Should I just make a fresh install?

What kind of details would you need?
rpm -qa ?
Comment 4 David Juran 2003-10-16 16:13:10 UTC 
Seems like the error only occurs when log in over remote X from my sunray, since
fonts are then missing.
Note You need to log in before you can comment on or make changes to this bug.