From owner-freebsd-ports@FreeBSD.ORG Sun Aug 31 08:03:30 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 76D28FB9; Sun, 31 Aug 2014 08:03:30 +0000 (UTC) Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 354501761; Sun, 31 Aug 2014 08:03:29 +0000 (UTC) Received: from fwd01.aul.t-online.de (fwd01.aul.t-online.de [172.20.27.147]) by mailout07.t-online.de (Postfix) with SMTP id 5CD2345E341; Sun, 31 Aug 2014 09:58:02 +0200 (CEST) Received: from [192.168.119.33] (r1QR3vZXYhfIzedxgpBaSLj9aCeXN+9XOR1zIvNHf-kpNWN6fB044O9VUoQ7VTaZdK@[84.154.101.219]) by fwd01.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XO01P-0CZqhU0; Sun, 31 Aug 2014 09:57:59 +0200 Message-ID: <5402D585.9050200@freebsd.org> Date: Sun, 31 Aug 2014 09:57:57 +0200 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd , Stefan Esser Subject: Re: [Analyzed] Re: Problem with xorg References: <1409238190.56909.YahooMailNeo@web140904.mail.bf1.yahoo.com> <53FF6A32.6020509@freebsd.org> <5402C685.1030507@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ID: r1QR3vZXYhfIzedxgpBaSLj9aCeXN+9XOR1zIvNHf-kpNWN6fB044O9VUoQ7VTaZdK X-TOI-MSGID: 54c55cfc-9f9e-47aa-9c2d-aa64d55c7ea0 Cc: "stable@freebsd.org" , x11@freebsd.org, Filippo Moretti , Ports FreeBSD X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2014 08:03:30 -0000 Am 31.08.2014 um 09:45 schrieb Adrian Chadd: > Ok, so what can we do right now to not have unicode characters in say, > the US keymap file? The "normal" US keyboard (/usr/share/vt/keymaps/us.kbd) does not contain characters >= 0x100. There is no problem even with ISO8859-1 characters used in many European countries, since they all are in the range 0x00 to 0xff. A problem is European keyboards with teh Euro sign (0x20ac) or e.g. Cyrillic or Greek keyboards, where many characters are >= 0x100. > (Just a local change, not committed anywhere - I agree it needs to be > fixed in the xorg code.) I'm wondering whether it might make sense to have the work-around committed to the xf86-input-keyboard port. People will waste time trying to understand, why their X server stops working when they select a keyboard layout with problematic characters for use with vt. This was not possible until a few weeks ago, since there were no such keymaps committed to vt/keymaps. If you had a keymap defined in rc.conf, then the name that used to work with syscons did not work with vt, but was just ignored (and the compiled in default US keyboard layout was used). I plan to commit a change to rc.d/syscons, soon, which will allow vt to be used with syscons keymap names (which are then internally converted to vt keymap names). With that change to rc.d/syscons, people will have their localized keyboard layout under vt, but will not be able to a local X11 server, anymore ... So I'm considering to commit the work-around patch, since a single missing key (under plain X11 - e.g. KDE works with all keys) will be just a minor violation of POLA, compared to no X11 at all. Regards, STefan