From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
in text mode, on TTY1 for example, keyboard set as fr-latin1, choice of the
language in the install program in French, doesn't write Euro symbol (AltGr+e),
and some french symbols too (ï¿½, ï¿½, ï¿½)
Backspace touch delete a part of the prompt line ([root@liocourt-test root]#
becomes [root@liocou )
Under X, no problem.
The same problem is existing on 8.0 (Psyche)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.log in on tty1
2.choose your keyboard as fr-latin1 with kbdconfig
3.type <alt Gr> + e -> gives e and not ï¿½
4. type ^ and e after -> gives nothing printed on the screen, should give ï¿½
Actual Results: <alt Gr> + e -> gives e and not ï¿½
typing ^ and e after -> gives nothing printed on the screen, should give a "e"
with a "^" on it. The same for "a" and "u"
Expected Results: ï¿½ symbol
ï¿½, ï¿½, ï¿½
keyboard mapping problem, or usage of UTF8 instead of ASCII, or font with
symbols not implemented maybe
I tried to change the font, nothing better, I tried to use the console-tools
package of the 7.3, replacing UTF with ASCII and choosing another font, it works.
according to the kbd faq in /usr/share, the euro and compose maps are not loaded
by default. look at the euro1.inc and euro2.inc and the compose inc maps in
/lib/kbd/keymaps/include and /lib/kbd/keymaps/i386/include and use loadkeys to
LANG=fr_FR.UTF-8 ls -l shows accent properly (not a font problem)
keymap is "us-acentos". I loaded /lib/kbd/keymaps/include/compose.latin1 by hand
with loadkeys. The compose key is "Ctrl+." (see output of "dumpkeys | grep -C4
Try getting an "e acute" accentuated character with "Compose + ' + e". I get
nothing printed on the screen.
uname tells me the kernel is 2.4.20-2.30 from rawhide. Problem is reproduceable
with an up to date kernel from 8.0.
Linux VT code doesn't support multibyte (i.e. UTF-8) results of
compose or dead keys *at all*.
So this is a duplicate of 75811. I unfortunately didn't have
time to fullfil the promise there.
*** This bug has been marked as a duplicate of 75811 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.