Bug 75229 - System font not working with cf
System font not working with cf
Product: Red Hat Linux
Classification: Retired
Component: kbd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
Depends On:
  Show dependency treegraph
Reported: 2002-10-05 15:11 EDT by Christian Lepine
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-17 04:21:11 EDT
Type: ---
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 Christian Lepine 2002-10-05 15:11:42 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
With the keymap cf, I can not obtain some caracters like (` and h) when in
console mode.
It was working fine with RH7.3

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

How reproducible:

Steps to Reproduce:
1.configure keyboard with cf
2.make sure SYSFONT="latarcyrheb-sun16" default after installation
3.try to get caracter ` or h with ` and a or ` and e

Actual Results:  no caracters or just a

Expected Results:  ` or h

Additional info:
Comment 1 Christian Lepine 2002-10-06 09:11:27 EDT
With that sysfont I can not use dialog nor can I read somme special messages. 
Caracters are wrong.
Comment 2 Owen Taylor 2002-10-06 12:44:07 EDT
Bill - could you assign this to the appropriate component?
Comment 3 Eido Inoue 2004-02-26 20:29:10 EST
should be fixed in 1.12-1, but I don't have the hardware to test this
Comment 4 Miloslav Trmač 2005-02-18 09:44:59 EST
Is this is still an issue?

If so, what locale are you using? Please attach the output of (locale).
The kernel currently doesn't support dead keys or compose sequences with UTF-8;
using iso-8859-1 it seems to work fine (except for `h, for which is no compose
Comment 5 Miloslav Trmač 2005-04-17 04:21:11 EDT
Please reopen this report if you can reproduce the problem on a recent release
and you can provide the requested data.

Thank you.

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