--qFgkTsE6LiHkLPZw
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Guten Morgen!=20
Sorry I forgot to CC my last mail.

On Fri, Mar 16, 2007 at 08:15:58AM +0100, Thomas Klausner wrote:
> Well, it doesn't. I set up my environment so that it displays everything
> fine in an UTF-8 enabled terminal (xterm or mlterm), but on the console
> I see two "A" and a diamond symbol where I would expect an "=E4".

Oh pardon, I didn't outline that, unfortunately, only your ASCII characters=
 will work in console, namely:

!"#$%&'()*+,-./0123456789:;<=3D>?
@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_
`abcdefghijklmnopqrstuvwxyz{|}~=20

=2E.because they overlap in both UTF-8 and ISO-8859 (or similar).

> Please send me more details about your setup.
> My test case is:
> bash
> export LC_CTYPE=3Dde_DE.UTF-8
> less "a file encoded in UTF-8"

less is linked against libtermcap and libc, but IFAICT they do not provide =
for UTF-8.
My setup you can find here -> http://wiki.netbsd.se/index.php/Unicode

What's with this uwscons thingie, any idea where to get it?

Johann

Johann

--
http://users.bsdprojects.net/~jfranz/

--qFgkTsE6LiHkLPZw
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (NetBSD)

iD8DBQFF+lqPF4uYH7Y/ZS4RArzPAKCHoBjQqNSmGMcNe1K/KeaDiF5yNgCeMw2u
FfuuTc/m+aicf2n4PuaRbN4=
=hS+r
-----END PGP SIGNATURE-----

--qFgkTsE6LiHkLPZw--