Re: i18n/locales hell

>=20
> I happen to be a German native....

I suspected that. Name doesn't sound that dutch.

>=20
> With vim you use ^K as compose character (stoopid Intel PCs lack a real=
=20
> keyboard).
>=20
> <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.
>=20
> etc... all in ISO 8859-1. Works on the console, in an xterm, even with =
KDE.

on gnome-terminal ^K (which I understand as ctrl-K) won't work.
what _does_ work on gterm is ctrl-shift-ascii-hexcode... not nice exactly.

Apart from that -  it would be nice if I could just use UTF8 everywhere. =
would
make things a lot easier.