On Wed, Jan 29, 2014 at 2:09 PM, Dietmar Maurer wrote:
> > Now, let's say the user connects from their Android device to the same
> VM while
> > on the road. If the VM is set to use QWERTZ, but I am using the "common"
> > layout file that is under discussion
>
> I think you are confused. Nobody u
> Now, let's say the user connects from their Android device to the same VM
> while
> on the road. If the VM is set to use QWERTZ, but I am using the "common"
> layout file that is under discussion
I think you are confused. Nobody used the 'common' layout. Instead, that file is
used as default ma
> We're discussing (for example) a German user who has picked QWERTZ inside
> their VM so that when they're connecting from their laptop which also has
> QWERTZ, everything is sane.
> Now, let's say the user connects from their Android device to the same VM
> while
> on the road. If the VM is set
Hi Dietmar,
Another case in point.
On Wed, Jan 29, 2014 at 12:08 AM, Dietmar Maurer wrote:
> I am not sure why you want to depend on the andriod keyboard layout?
>
I do not. Users can pick whatever layout they please on their device.
Opaque and aSPICE receive a KeyEvent from which a unicode val
> So it certainly doesn't cover all the cases (QWERTZ, AZERTY, etc) that
> Opaque/aSPICE need to cover!
I am not sure why you want to depend on the andriod keyboard layout?
Simply set the VM to use a QWERTZ keyboard, and use the same layout
with oqaque?
Or do you want to emulate android devices
Hi Dietmar,
But that common file would work only for QWERTY!
#
# QWERTY first row
#
...
#
# QWERTY second row
#
...
#
# QWERTY third row
#
...
So it certainly doesn't cover all the cases (QWERTZ, AZERTY, etc) that
Opaque/aSPICE need to cover!
iordan
On Tue, Jan 28, 2014 at 12:42 AM, Dietmar
> Case in point. Let's consider:
> /usr/share/qemu/keymaps/de
> The user wants to input the letter "q" from their Android device. Since this
> is
> QWERZ, I need a mapping of unicode 0x71 to scancode 0x10.
> All I can find in /usr/share/qemu/keymaps/de that mentions 0x10 is the "at"
> symbol with
Hi Dietmar,
Case in point. Let's consider:
/usr/share/qemu/keymaps/de
The user wants to input the letter "q" from their Android device. Since
this is QWERZ, I need a mapping of unicode 0x71 to scancode 0x10.
All I can find in /usr/share/qemu/keymaps/de that mentions 0x10 is the "at"
symbol with
Not sure if I understand your question. Those files have mappings for letters
and numbers.
You can look up the used names in /usr/include/X11/keysymdef.h file.
I use a small script to extract those name->unicode mappings:
https://git.proxmox.com/?p=spiceterm.git;a=blob;f=genkeysym.pl;h=cdccf3cf
Hi Dietmar,
Thanks for your suggestion. These keymap files appear to describe how to
effect special characters to the VM, but I don't see any description of
unicode characters representing letters and numbers. What did you use for
that purpose?
It's a useful resource for a cross-check in any case
> I really didn't like the idea of releasing Opaque (the oVirt/RHEV VM console
> Android client) into production supporting only English (QWERTY), so I decided
> to implement a workaround for the existing inability to send Unicode directly
> to
> the OS of the VMs. It's not perfect, because it req
Hi guys,
Some of you may have seen most of this in my posting on the ovirt-users
mailing list. I wanted to inform the spice-devel list separately, in order
to hear your input on the topic as it concerns SPICE directly.
I really didn't like the idea of releasing Opaque (the oVirt/RHEV VM
console A
12 matches
Mail list logo
