Typing suggestions much worse than android default keyboard.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Regular typing on landscape or portrait with typing suggestions on.
2.
3.

What is the expected output? What do you see instead?
-> Since the description says (and the keyboard looks like) it borrows a lot 
from the default android keyboard source, I was expecting the prediction / 
typing suggestions to be the same (or perhaps better) than the default.  This 
is not so.  Also, on the default keyboard, typing two spaces in a row inserts a 
period and a space -a very handy feature- while this keyboard does not do that.

What version of the product are you using? On what operating system?
-> Hacker's Keyboard v1.11 (latest version in market as of 2011/may/24.  
Android 2.3.4 on a Nexus S.

Please provide any additional information below.
-> Hmm. I am relatively new to android and jumped in at 2.3 .. Maybe the 
original keyboard source for Hacker's Keyboard came from a 2.2 and that is why 
I notice these differences? 

Anyway, good effort for sure.  Just trying to pitch in my 2c in return for your 
hard work.

Original issue reported on code.google.com by mrgv...@gmail.com on 24 May 2011 at 8:29

[GoogleCodeExporter]

It is based on the Gingerbread AOSP source which should correspond to 2.3.

Can you please verify the keyboard options? (Via the "gear" key in the bottom 
left of the keyboard.) You should have all the same settings available as in 
the original Gingerbread keyboard, but the defaults may be different. 
Specifically, check if the Quick Fixes setting is on. I do get period+space 
when pressing space twice.

Or are you referring to word suggestions? Which language are you using? The 
keyboard currently contains the US English dictionary from Cyanogen and no 
other languages. The Gingerbread AOSP release does not include the 
dictionaries, so there may be differences in dictionary content. Do you have an 
example for the expected and actual suggestions you're getting?

Original comment by Klaus.We...@gmail.com on 25 May 2011 at 5:30

• Changed state: Accepted

[GoogleCodeExporter]

I was testing and found out that Hacker's Keyboard (HK) only goes haywire when 
capitalized words are used:

I type "th" and the keyboard is suggesting the following list:
(the that this they there their them ...)
I type "thi" and get the following suggestions:
(this think thing things thirty third ...)

So far, so good.  This behavior is the same on the default android keyboard 
(AK) and HK. BUT, HK gets thrown off by the use of capitalized letters...

I type "Th" and HK gives the following suggestions:
(Thomas Thu TN Thomson Thai RH Theresa ...)
I type "Thi" and HK gives the following suggestions:
(Thu Thursday Thomas Thompson FBI Thomson ...)

Note two things:
1. AK still gives the same auto-complete suggestions on the capitalized words.
2. HK is not only suggesting different words, but apparently handling the 
situation incorrectly and suggesting words that are not nearly as likely or 
useful.

Not sure if it's as simple as how the words are ordered in the dictionary file 
or if something in the actual code needs to handle lower/upper cases 
differently than it does now.

Hope this helps pinpoint the bug.

Original comment by mrgv...@gmail.com on 25 May 2011 at 3:13

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

One more interesting capitalization+auto-complete issue: At the end of 
sentences (or, at least, the last word before punctuation), auto-complete seems 
to want to capitalize words.  I'll try and reproduce, but wasn't able to do so 
just now.

Original comment by bli...@google.com on 27 May 2011 at 4:59

[GoogleCodeExporter]

This issue was closed by revision be970a96265b.

Original comment by klausw@google.com on 28 May 2011 at 6:11

• Changed state: Fixed

[GoogleCodeExporter]

The capitalization glitch should be fixed in the latest version (v1.12rc7): 
http://code.google.com/p/hackerskeyboard/issues/list

Adam, can you see if you're still seeing your issue? It sounds related, so it's 
possible that it had the same underlying cause, but I couldn't reproduce it. If 
it's still happening, please file a new issue.

Original comment by Klaus.We...@gmail.com on 28 May 2011 at 6:32

[GoogleCodeExporter]

Adam, I think I can now reproduce your issue, it's apparently not fixed yet. 
See issue 18.

Original comment by Klaus.We...@gmail.com on 28 May 2011 at 8:19

[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