Removing the space when trying to add smiley faces

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Simply input data, then add a space and then a colon or semicolon.
2. Example: if I type "Hey, what's up? :)", the following will show up
3. "Hey, what's up?:)"

What is the expected behavior? What do you see instead?
-Expected behavior would leave the space so that the colon or semicolon was not 
attached the last word and would create a face. Instead, the space between the 
last word and the colon/semicolon is automatically removed as a 
spelling/grammar error so that it is attached.

What version of Hacker's Keyboard are you using? (See "Debug" section at
the bottom of the app's Settings menu.)
On what phone or tablet?
-Version 1.31.1331 065ed34b811c 2012-02-24, from Samsung galaxy S2 epic touch 
4g, full stock no roms.

If applicable, does this affect the 4-row or 5-row layout, or both? Which
language(s)?
-I would assume this affects both, however I only really use the 4-row portrait 
mode. English language.

Please provide any additional information below.
-A very minor bug, but as I'm one to send quite a few smiley faces throughout a 
conversations, it does suck to have to type it out, then backspace to get rid 
of it and retype it everytime :). Thanks!

-Off topic: Absolutely amazing keyboard!

Original issue reported on code.google.com by Matt.Bu...@gmail.com on 3 Jul 2012 at 5:21

• Merged into: #164

[GoogleCodeExporter]

You should try using suggestions without auto-correct, that keeps spaces you 
type unchanged. More here: 
https://code.google.com/p/hackerskeyboard/issues/detail?id=164#c1

Original comment by Klaus.We...@gmail.com on 3 Jul 2012 at 6:00

[GoogleCodeExporter]

Thanks for the input. I gave it a shot, however the way I type on phone is fast 
with relying on auto-correct to make small changes. Is there any way to find a 
common medium where auto-correct is still on but the auto-correction is not 
implemented? Perhaps this is a tall order and I apologize for that. Just 
thought I'd throw it in. Regardless. Excellent keyboard that I will be keeping. 
:)

Original comment by Matt.Bu...@gmail.com on 3 Jul 2012 at 6:29

[GoogleCodeExporter]

Honestly, the more I play with it, the less of an issue it becomes as I 
automatically find myself correcting for it. The last thing I would want is to 
add cumbersome options and coding to the program. :)

Original comment by Matt.Bu...@gmail.com on 3 Jul 2012 at 6:36

[GoogleCodeExporter]

The core problem is that the space bar is dual-purpose in autocomplete mode - 
it doesn't just insert a space, it also accepts the current completion and 
inserts a "soft space" after it, and the soft space then gets swapped when it's 
followed by punctuation. Imagine typing "Test something" vs. "Test: " vs. "Test 
:-)". In each case the autocomplete will initially end up with "Test ", and in 
the 2nd case it'll remove the space.

Original comment by Klaus.We...@gmail.com on 3 Jul 2012 at 8:59

• Changed state: Duplicate