filipst / hackerskeyboard

Automatically exported from code.google.com/p/hackerskeyboard
0 stars 0 forks source link

Unusual placement of Polish characters #129

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
(Introduction)
Polish alphabet has some national characters. Among them there are two 
similiar: "ż" and "ź". The first one is used more often than the other one. 
That's why in order to produce "ż" on Polish keyboard, ALT+Z has to be 
pressed, and ALT+X for "ź".

In Hacker's Keyboard both characters are accessible by long-pressing "z" and 
they're presented in reverse order.

What steps will reproduce the problem?
1. Press and hold "z"
2. Press and hold "x"

What is the expected behavior? What do you see instead?
Expected: suggestion of "ż" after pressing "z" and "ź" after pressing "x".
Result: suggestion of "ź,ż" after pressing "z" and nothing on "x".

What version of Hacker's Keyboard are you using? (See top of the app's
Settings menu.) On what phone or tablet?
1.27.1145 (from 6th November 2011) on Asus eeePad Transformer tablet

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

Please provide any additional information below.
If you're considering implementing AltGr behaviour, please keep in mind this 
issue.

Original issue reported on code.google.com by ja...@holubinka.pl on 18 Dec 2011 at 6:28

GoogleCodeExporter commented 9 years ago
I had attempted to do this in revision e51027c55842 in relation to issue 87, 
but it appears that I got it backwards. Trying again in revision 0a7416eddb84.

Please try version 1.28rc5 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list and let me know if that 
works as expected for you.

Original comment by Klaus.We...@gmail.com on 21 Dec 2011 at 9:34

GoogleCodeExporter commented 9 years ago
Works fine on 1.28rc5.

Thanks a lot!

Original comment by ja...@holubinka.pl on 21 Dec 2011 at 9:47

GoogleCodeExporter commented 9 years ago
[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

GoogleCodeExporter commented 9 years ago
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 commented 9 years ago
Bulk update - changing "Fixed" to "Verified" for old bugs.

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