--===============1983316777==
Content-Type: multipart/signed;
  boundary="nextPart2313033.V3hVnAlDf9";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2313033.V3hVnAlDf9
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> [: Jason Harris :]
> [...] Is it an encoding problem?  Is his system somehow setup to use=20
> ascii encoding instead of utf-8?  I tried to find such a setting in the
> Control Center, but I didn't see anything.

I had a similar experience with list of FOV symbols in the menu -- if my=20
locale encoding was not UTF-8, I would get strange characters there=20
(typical UTF-8 rendered as ASCII junk). As soon as locale was set properly=
=20
(eg. LC_ALL=3Dsr_CS.UTF-8 in ~/.bash_profile), the problem disappeared.

To my knowledge, locale cannot be set through Control center, but only in=20
login shell.

=2D-=20
Chusslove Illich (=D0=A7=D0=B0=D1=81=D0=BB=D0=B0=D0=B2 =D0=98=D0=BB=D0=B8=
=D1=9B)

--nextPart2313033.V3hVnAlDf9
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBFA/4rMSGXgigGr3ERAgjtAKCOn+lLCUHAJ8Zesjsr9hJ8NJJ/ngCdGnpu
1FKtE/T1pGVeoNazs8/ki8w=
=QnAJ
-----END PGP SIGNATURE-----

--nextPart2313033.V3hVnAlDf9--

--===============1983316777==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1983316777==--