Re: i18n/locales hell
"Daniel C. von Asmuth" <asmuth-8LkvcxCLB6JmR6Xm/[email protected]> Wed, 14 Jan 2004 23:42:52 +0100
| Newsgroups | gmane.linux.usability.annoyances |
|---|---|
| Message-ID | <[email protected]> |
Also schrieb Dexter Filmore am Mit, den 14. Jan 2004 um 01:46:48 nachmitt= ags: >=20 > So I'm not a native english speaker, I'm from germany.=20 > I write my private mails in german, I visit german chat rooms every now= and > then. > Some files have special characters in it. >=20 > Special characters. >=20 > Namely: =F6=E4=FC=D6=C4=DC plus one KDE isn't capable of displaying rig= ht now, and here's > my point: >=20 > I'm bloody tired of it. >=20 > I want *ONE* system wide configuration for i18n/locales. > But: I need to adjust i18n for: tty, X, xterm, gnome-terminal, KDE kons= ole, > per application, for Gnome, for KDE, for god knows what.=20 > All my i18n was almost fine until yesterday when I decided to switch to= KDE. I happen to be a German native.... With vim you use ^K as compose character (stoopid Intel PCs lack a real=20 keyboard). <compose>o" gives =F6. <compose>"A gives =C4. <compose>ss gives =DF. <compose>,c gives =E7. <compose>~N gives =D1. <compose>oe gives =F7. <compose>/o gives =F8.=20 <compose>^u gives =FB, <compose>'e gives =E9. <compose> `a gives =E0. etc... all in ISO 8859-1. Works on the console, in an xterm, even with KD= E. Kind regards, Daniel von Asmuth --=20 Stop the peace!