From owner-freebsd-current@FreeBSD.ORG Tue Nov 9 17:45:43 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1A591065673 for ; Tue, 9 Nov 2010 17:45:43 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (unknown [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id 472A48FC19 for ; Tue, 9 Nov 2010 17:45:43 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id 6B5322A28CEA; Tue, 9 Nov 2010 18:45:42 +0100 (CET) Date: Tue, 9 Nov 2010 18:45:42 +0100 From: Ed Schouten To: Renato Botelho Message-ID: <20101109174542.GM2054@hoeg.nl> References: <20101109100319.GV2054@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UZwaptqO+BtzVOeY" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Eir Nym , FreeBSD Mail Lists Subject: Re: Syscons and termcap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 17:45:43 -0000 --UZwaptqO+BtzVOeY Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Renato Botelho , 20101109 17:08: > Well, few weeks ago I moved from ISO-8859-1 to UTF-8 on my Xorg > environment, and after reading this I decided to make a test. >=20 > I rebuilt my 9.0-current (r215031) with option TEKEN_UTF8 in kernel > config, and after configure my syscons to use cp850-* fonts i can > see UTF-8 chars properly \o/ Well, the point here is that it just performs some really hackish translation to CP437, not CP850, on the output path. It is really not robust. Copy-pasting is also broken because of it, because it pastes CP437 characters. > The only thing i cannot do here is to type chars with accent like =E1=E9 > on console, because it seems to don't respect deadkeys, when I > press ' the char ' is show and never wait the next char to compose > a new one when necessary. Is it a knwon issue or i'm doing > something wrong? This is a known issue, since there is no translation from Unicode code points to UTF-8 sequences. In other words, if you press =EB, the keyboard layer will properly send a 235 to Syscons, but instead of encoding it as 0xC3 0xA9, will just emit a single byte, having value 0xE9. Maybe a patch like this could already get that working, but it's just a quick hack. http://80386.nl/pub/syscons-utf8.txt Greetings, --=20 Ed Schouten WWW: http://80386.nl/ --UZwaptqO+BtzVOeY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkzZiMYACgkQ52SDGA2eCwX9mwCePYMo6g9ZpNm6i4Co6R8sWxaT r9IAnR3YMLIPIyI5BRiNUMFVRfunJjB0 =2SLm -----END PGP SIGNATURE----- --UZwaptqO+BtzVOeY--