From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 21 18:39:20 2014 Return-Path: Delivered-To: freebsd-hackers@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 25B9C8A1 for ; Thu, 21 Aug 2014 18:39:20 +0000 (UTC) Received: from mail-ie0-x244.google.com (mail-ie0-x244.google.com [IPv6:2607:f8b0:4001:c03::244]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ED67637FD for ; Thu, 21 Aug 2014 18:39:19 +0000 (UTC) Received: by mail-ie0-f196.google.com with SMTP id rp18so1168305iec.11 for ; Thu, 21 Aug 2014 11:39:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DwUpANODZd3CVEXnkxLakK/oaju7GohGj469HAUA1Pk=; b=pjKddUCrEpkfT9NWKi9lAAXh0kefqalAYmXGBq+c19aiAmGhzSgDyKhkCipAyrFQfY Kafx38ZgbAKOARjDLhq4hn4rHwOr3aTyFgg6J8jhYjEseYNV+KX3otIRLKxeJEe2eV3d 4Rbsh3+M6Q5vEboTNjN4apQdaY6/QASKuXqiRN+mDswNPjExZbkK8LFLCbSybZLfcixv Wexze3lPF77FGL0TvD4sap61DYVmfS6xhzjGQbgGNxfZnvMFNcyNiJebXqNuLG1meLeC GTo+quaUrWWKl+JqlJPBFK7WNdyR8gd8KnqMV+lq6QUVq71fPAIcwcYWp8JFo5J7M7DB +SoQ== MIME-Version: 1.0 X-Received: by 10.42.63.129 with SMTP id c1mr2464551ici.82.1408646359495; Thu, 21 Aug 2014 11:39:19 -0700 (PDT) Received: by 10.64.26.130 with HTTP; Thu, 21 Aug 2014 11:39:19 -0700 (PDT) Date: Thu, 21 Aug 2014 11:39:19 -0700 Message-ID: Subject: Re: Keymap definitions for VT / NEWCONS From: Dieter BSD To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 18:39:20 -0000 > And it is so much easier to use the country code that you most > probably know from your mail or web address Where do I apply for my .com passport? > than the locale code, which many users never get to see. Most users have never heard of a "locale" in a computer context. How often do most people have to deal with the filename for their keyboard? Almost never. Nice filenames are a good thing, but these filenames are not the most important ones in the universe. Just make them logical, extensible, and not excessively long (e.g. ipv6 addresses). The important part is to make it easy to find out what file you need to use. A plain text file containing a list of filenames and the corresponding languages, countries, and whatever else will do the job. Make it easy to find the index file by including its pathname in the documentation. If you want to hurt yourself, then write a little utility to help find the filename. If you must worry about names, "NEWCONS" could use improvement. What will the next system be called" NEWNEWCONS? VERYNEWCONS, followed by ULTRANEWCONS, followed by UeBERNEWCONS? The more important problem is, does this "NEWCONS" thingy provide a way to correct errors? For example, I am using a proper Unix keyboard, but for some reason both the firmware and FreeBSD think it is a horrid pee-cee style keyboard. ~/.xmodmap can fix this up, but only for X. Does this "NEWCONS" thingy provide xmodmap type functionality? > And de_CH and fr_CH differ just in whether " Another problem is that whatever characters those are do not display properly in an xterm window. And pasting them into emacs doesn't work either.