qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Programmingkid <programmingkidx@gmail.com>,
	Scott Wood <scottwood@freescale.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	The OpenBIOS Mailinglist <openbios@openbios.org>,
	"qemu-ppc@nongnu.org list:PowerPC" <qemu-ppc@nongnu.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc]  Mac OS X on QEMU
Date: Wed, 10 Jul 2013 18:28:31 -0500	[thread overview]
Message-ID: <87zjtukna8.fsf@codemonkey.ws> (raw)
In-Reply-To: <E340429D-2C4C-4D36-8A92-9C5A37742FB8@gmail.com>

Programmingkid <programmingkidx@gmail.com> writes:

> On Jul 10, 2013, at 4:17 PM, Scott Wood wrote:
>
>> Keyboards don't generally speak ASCII (or Unicode).  They produce keycodes, which are generally translated into some sort of event by the host's input layer (e.g. the X server).  It's up to the guest software to translate those keycodes into either ASCII or Unicode (or whatever else it wants).
>
> Thanks for this info. The ascii system does work on a PC environment.

This thread is confusing presumably because people are mixing up topics.

The Windows key is the same thing as the Command key.  As Scott already
mentioned, there is no physical difference between an Apple and PC
keyboard except for stickers on the keys.  On a PC keyboard, the sticker
is a Windows logo.  On an Apple keyboard, it's the Command logo.

If the Windows key is not injecting a Command key, it's a bug.  This
should work just fine with the GTK UI.  I have no idea about Cocoa if
that's what you're using.

ASCII has nothing to do with keyboards.  It's a character encoding.

Regards,

Anthony Liguori

  parent reply	other threads:[~2013-07-10 23:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2E45432C-6960-4E72-9F28-9848DF8A709A@gmail.com>
2013-07-04 14:45 ` [Qemu-devel] [Qemu-ppc] Mac OS X on QEMU Alexander Graf
2013-07-04 14:51   ` Stefan Hajnoczi
2013-07-04 14:58     ` Programmingkid
2013-07-09 17:32       ` Scott Wood
2013-07-10  3:36         ` Programmingkid
2013-07-10  4:10           ` [Qemu-devel] [OpenBIOS] " Tarl Neustaedter
2013-07-10 14:16             ` Programmingkid
2013-07-10 19:03           ` [Qemu-devel] " Scott Wood
2013-07-10 19:54             ` Programmingkid
2013-07-10 20:17               ` Scott Wood
2013-07-10 20:55                 ` Programmingkid
2013-07-10 21:12                   ` Scott Wood
2013-07-10 23:28                   ` Anthony Liguori [this message]
2013-07-11  1:43                     ` Programmingkid
2013-07-10 22:01               ` Alexander Graf
2013-07-10 23:35                 ` Anthony Liguori
2013-07-04 14:52   ` Programmingkid

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=87zjtukna8.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=openbios@openbios.org \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=scottwood@freescale.com \
    --cc=stefanha@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).