REGRESSION: Thai keyboard

[GoogleCodeExporter]

Background info:
Also see Issue 72 which has a fix for the keyboard layout pending plus a 
dictionary.

What steps will reproduce the problem?

type any word with vowels/symbols above a consonant. The typing order for the 
symbols is opposite of standard keyboard behaviour.

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

Thai script has vowels which can be place before, after, above and/or below 
consonants. The standard behaviour on a keyboard is to type characters in this 
order:

- vowel before consonant (if applicable)
- consonant
- vowel symbol below consonant (if applicable)
- vowel symbol above consonant (if applicable)
- other symbols above consonant (if applicable)

This fails on the latest version (and maybe others, untested) but did work on 
the first release of the Thai layout.

eg. word ก็ should be typed ก + ็ but instead hacker's keyboard 
requires it to be typed ็ + ก which is incorrect.

What version of Hacker's Keyboard are you using? (See top of the app's
Settings menu.) On what phone or tablet?

tablet (Xoom, android 3.1)
v1.27

If applicable, does this affect the 4-row or 5-row layout, or both? Which
language(s)?

5-row

Please provide any additional information below.

Original issue reported on code.google.com by hmm...@gmail.com on 22 Nov 2011 at 8:20

[GoogleCodeExporter]

I've reverted the behavior to the previous one by disabling the dead key logic 
added for Latin languages which typically enter the dead key first, followed by 
the character to be modified. See revision 06a7a2378fd9.

Please try version v1.28rc1 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list and let me know if that 
works better for you. This also includes the keymap tweaks from issue 72.

Original comment by Klaus.We...@gmail.com on 22 Nov 2011 at 10:37

• Changed state: FixInTest

[GoogleCodeExporter]

I can confirm v1.28rc1 fixes the problem.

Many thanks for your quick update.

(there are a few minor problems with the keymap tweaks - I'll post a comment on 
issue 72 separately, but need to do some more testing first)

Original comment by hmm...@gmail.com on 23 Nov 2011 at 8:08

[GoogleCodeExporter]

[Bulk bug update] The new Market release 1.29 includes the changes from the 
v1.28 prerelease series, and these "FixInTest" issues should now be fixed. If 
not, please reopen the bug with additional information. If the original bug 
covered multiple separate issues that aren't all addressed, please open new 
bug(s) for the leftover ones.

Original comment by Klaus.We...@gmail.com on 13 Jan 2012 at 9:29

• Changed state: Fixed

[GoogleCodeExporter]

Bulk update - changing "Fixed" to "Verified" for old bugs.

(Background: I'm changing the "Fixed" status to be considered open, the next 
steps in the lifecycle will be the closed states "FixInTest" and "Verified". 
This lets me mark issues as "Fixed" in commit messages without hiding them from 
the issue tracker.)

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:33

[GoogleCodeExporter]

Bulk update - changing "Fixed" to "Verified" for old bugs.

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:34

• Changed state: Verified