(*** This bug was imported into bugs.kde.org ***) Package: konsole Version: 1.1.2 (using KDE 3.0.2 ) Severity: normal Installed from: (3.0) Compiler: gcc version 2.95.4 20011002 (Debian prerelease) OS: Linux (i686) release 2.2.19 OS/Compiler notes: After "upgrading" to KDE3 there is no more Euro-Sign under konsole. Instead I have a question mark. In earlier versions it was possible to choose under the font dialog also the encoding. This possibility desappeared. I now have iso-8859-1 in the console but I want again iso-8859-15 and there is no way to set that. (I just noticed the possibility to choose the encoding seems to have desappeared in every kde application - very bad.) (Submitted via bugs.kde.org) (Called from KBugReport dialog)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 08 August 2002 20:20 goesele@hfph.mwn.de wrote: > Package: konsole > Version: 1.1.2 (using KDE 3.0.2 ) > Severity: normal > Installed from: (3.0) > Compiler: gcc version 2.95.4 20011002 (Debian prerelease) > OS: Linux (i686) release 2.2.19 > OS/Compiler notes: > > After "upgrading" to KDE3 there is no more Euro-Sign under > konsole. Instead I have a question mark. > > In earlier versions it was possible to choose under the font dialog also > the encoding. This possibility desappeared. > > I now have iso-8859-1 > in the console but > I want again iso-8859-15 and there is no way to set that. > > (I just noticed the possibility to choose the encoding > seems to have desappeared in every > kde application - very bad.) And you know why? It simply works. If your keyboard requests an euro symbol it gets one. So I bet your xev doesn't show KeyPress event serial 27 synthetic NO window 0x2800001 root 0x37 subw 0x2800002 time 2336857582 (6061) root:(1158810) state 0x2000 keycode 26 (keysym 0x20ac EuroSign) same_screen YES XLookupString gives 1 characters: "¤" when you press a euro sign. Greetings Stephan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9UsMcwFSBhlBjoJYRAtyaAKDRsOikr7NkT71AHroubPNfATrpWwCfeHnB Zbe3oG6FXXA7ZYgsOcvqpFs= =Bevb -----END PGP SIGNATURE-----
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"?
The problem is not the font encoding, the problem is the encoding used by the shell. I think it makes sense to add an encoding option to the configuration dialog of the different sessions. (Comparable to the config of $TERM)
Found the solution. Or rather, Ingo Kl
Solved.