[Konsole-devel] [Bug 46268] no more possible to set font encoding

[Alain Knaff]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=46268     




------- Additional Comments From kde at alk.org.lu  2003-04-21 22:50 -------
Stephan, I find your answer rather surprising, as it only addresses half of the problem: indeed a 
konsole is not only about input (supposedly addressed) but also about output. For instance, if 
you cat a file containing an 0xa4 character, how would konsole chose to display it? Would it 
show an euro sign (iso-latin-15), or the old crossed circle (iso-latin-1)? 
 
And, on further investigation, even the input side does not work (in KDE 3.1.1): If the character 
is entered using the keyboard (in which case there _is_ a different keysym, and it could 
conceivably work...), you get a question mark instead of a Euro Sign. 
 
xmodmap -e 'keysym s = s S s s EuroSign' 
 
(press AltGr-S) 
 
===> xev shows that it is indeed EuroSign: 
 
KeyRelease event, serial 27, synthetic NO, window 0x5400001, 
    root 0x70, subw 0x5400002, time 214463198, (43,42), root:(46,826), 
    state 0x80, keycode 39 (keysym 0x20ac, EuroSign), same_screen YES, 
    XLookupString gives 0 bytes:  "" 
 
However, console just interprets it as a question mark. 
 
The only strange thing in the xev output is the XLookupString. In case it matters, the X server 
is XFree86-server-4.3.0-15, as included with SuSE 8.2. 
 
So, why is there no way to set a code page? The old way (explicit setting) was preferable 
IMHO. 
Why not add it back either to konsole's own menu, or to the control center's "Regional & 
Accessibility Settings"?