From: Vojtech Pavlik <vojtech@suse.cz>
To: John Bradford <john@grabjohn.com>
Cc: aebr@win.tue.nl, ndiamond@wta.att.ne.jp, vojtech@suse.cz,
linux-kernel@vger.kernel.org
Subject: Re: Translated set 3
Date: Mon, 22 Sep 2003 15:50:20 +0200 [thread overview]
Message-ID: <20030922135020.GA1136@ucw.cz> (raw)
In-Reply-To: <200309221242.h8MCgtMf000302@81-2-122-30.bradfords.org.uk>
On Mon, Sep 22, 2003 at 01:42:55PM +0100, John Bradford wrote:
> Sorry if there is an obvious answer to this question that I'm missing,
> but what is the advantage of using translation in set 3?
>
> I totally agree that translated set 2 is the way to get 99% of
> keyboards working perfectly, and that the reason we use translation
> here, is because although untranslated set 2 is simpler, some laptops
> don't support this properly, and some that do have problems with BIOS
> interpretation of the codes, etc.
>
> However, surely setups that support set 3, will support it equally
> well with and without translation? Here, I don't see the advantage of
> enabling translation.
>
> Why not simplify the whole problem, and either have:
>
> * translated set 2 with workarounds for all known strange keyboards
> * untranslated set 3
Because it doesn't simplify the driver. :) The translated+set3 combo,
although doesn't make much sense, just works ...
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2003-09-22 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 12:42 Translated set 3 John Bradford
2003-09-22 13:50 ` Vojtech Pavlik [this message]
2003-09-22 20:25 ` Andries Brouwer
2003-09-23 17:26 ` Vojtech Pavlik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030922135020.GA1136@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox