DVORAK and AZERTY layouts should also affect the physical keyboard

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install and enable application with english and, say, dvorak
2. Switch input method to anysoftkeyboard
3. Switch layout to dvorak

What is the expected output? What do you see instead?

Onscreen keyboard is dvorak in portrait and landscape, but the physical
keyboard is still qwerty.  I was expecting the physical keyboard to switch
to dvorak also.

What version of the product are you using? On what operating system?

20091004-skipper (release 11) on Android 2.0, build ESD20

Please provide any additional information below:

It occurred to me that this may be outside the scope of this application,
in which case the last paragraph on
http://code.google.com/p/softkeyboard/wiki/HowTo is misleading.  "The
physical keyboard layout will be similar to the one currently selected in
Any Soft Keyboard on-screen keyboard."

Is this a matter of some layouts just having OSK versions but not physical
versions?  --Is physical dvorak for the Droid just unimplemented?

Original issue reported on code.google.com by Etha...@gmail.com on 15 Nov 2009 at 10:23

[GoogleCodeExporter]

Good to hear that ASK works on Droid :)

I wasn't sure that dvorak on the physical keyboard is a good idea when I 
implemented
that - physical keys labels etc...
But I see your problem with that. I think that I'll add an option for that.

It wont be ready for the next release

Original comment by menn...@gmail.com on 15 Nov 2009 at 10:56

• Changed title: DVORAK and AZERTY layouts should also affect the physical keyboard
• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm a first year computer programming student taking a Java class-- how long do 
you
think it would take me to familiarize myself with the Android APIs and your code
enough to be of real assistance?

Original comment by Etha...@gmail.com on 15 Nov 2009 at 11:04

[GoogleCodeExporter]

I believe that doing simple tasks (like fixing this issue) will not take a long 
time
- probably a week or so after you'll understand Java's interface, class, 
hashtable
concepts, and XML structure.

The biggest problems are the SVN and IDE setup issues.
I'm don't know how tech-savvy are you, but these could be a pain.

In any case, I'm OK with you trying to fix it, and I'm willing to tutor you.

Original comment by menn...@gmail.com on 15 Nov 2009 at 12:08

[GoogleCodeExporter]

Issue 205 has been merged into this issue.

Original comment by menn...@gmail.com on 6 Dec 2009 at 8:30

[GoogleCodeExporter]

@EthanA2, do you want to implement this?

Original comment by menn...@gmail.com on 19 Dec 2009 at 1:43

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I should try to get an IDE properly configured so I can implement things 
myself--

But this particular bug, meh.  I have realized that the main purpose of a 
physical 
keyboard is playing SNES and Genesis games in emulators :P  It's not physically 
possible to type as fast with a physical phone keyboard as I already type 
with ASK.

I'd actually be okay if this bug was set aside somehow, one could claim that 
keys 
should do what their labels say they'll do, but somebody else might want this 
feature 
at some point..

Original comment by Etha...@gmail.com on 20 Dec 2009 at 2:37

[GoogleCodeExporter]

You have a point. Maybe it should be turned on by check-box.

I'll remove it from the release.

Original comment by menn...@gmail.com on 20 Dec 2009 at 2:40

[GoogleCodeExporter]

I would like this to be implemented (but sadly can't offer to help). In the 
meantime the text on the wiki ought to 
be removed/edited, IMO, as the physical kb doesn't seem affected by this 
software.

Original comment by paulm%pa...@gtempaccount.com on 29 Dec 2009 at 3:02

[GoogleCodeExporter]

I would like to see this be implemented for the physical keyboard.  Many type 
in Dvorak on Qwerty keyboards without looking at the keys, and could do the 
same on their phones keyboards.  Typing fast is all about muscle memory.

Original comment by markbrag...@gmail.com on 18 Sep 2010 at 3:25

[GoogleCodeExporter]

Hello,

i'm using the Archos 101 with Android 2.2, i am glad that the virtual keyboard 
is now AZERTY but my physical keyboard is still QWERTY, is there allready a 
solution for this issue?

Many thanks

Gertos.

Original comment by kingger...@gmail.com on 16 Dec 2010 at 5:44

[GoogleCodeExporter]

Just to +1 this, it's useful for anyone using Dvorak on an external physical 
keyboard (not just for phones with physical keyboards.)

There'll be more of us as pads/tablets become more widespread!

Original comment by nick.cu...@gmail.com on 5 Sep 2011 at 1:45

[GoogleCodeExporter]

What if future versions of the Android phone which have a physical keyboard 
have their keys over an LCD-screen (possibly with touch, but this Could be done 
without it) that automatically changes with the keyboard-layout?  This would 
make localized keyboard-maps (Icelandic, Hebrew, Arabic, etc.) as well as 
non-QWERTY versions much more easily implemented.   

Original comment by swey...@gmail.com on 3 Nov 2011 at 1:15