Typing with Swype: I auto capitalizes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using Swype keyboard
2. Tap type, don't Swype (as you do for non-words)
3. Use the letter I (even CTRL+I for Tab)
4. Even worse if using Tab for auto complete. The filename will auto complete 
but when you press space or enter, it removes the trailing slash and inserts a 
capital I.

What is the expected output? What do you see instead?
 Expected: a lowercase I ("i") or a Tab character if you just pressed CTRL.
Happens: Capital Is the middle of words, or auto completed paths get adorned 
with I once you start the next action (usually space or enter).

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
1.7.1

What type of system are you trying to connect to?
Unix bash shell.

If you are able to connect, what is the output of "echo $TERM":  screen
"uname -a": Linux vm8 2.6.26-2-amd64 #1 SMP Tue Jan 25 05:59:43 UTC 2011 x86_64 
GNU/Linux 

and any other relevant information on the host?

Please provide any additional information below.

Original issue reported on code.google.com by r...@hambrook.co.nz on 15 Sep 2011 at 11:12

[GoogleCodeExporter]

Sorry, I just updated my Swype installation and it fixed most of my issues. 
Sorry for my bogus report. Love Connectbot, use it all the time.

Original comment by r...@hambrook.co.nz on 15 Sep 2011 at 11:59

[GoogleCodeExporter]

I have the same issue with the capital I appearing instead of the lowercase I. 
Using Galaxy tab 10.1 with swipe keypad. Otherwise excellent.

Original comment by primexa...@gmail.com on 3 Jan 2012 at 6:55

[GoogleCodeExporter]

primexa...@gmail.com... I posted this bug without properly thinking. Once I 
updated Swype the issue went away. I don't know if the Galaxy Tab 10.1 came 
with Swype pre-installed or not but if you're able to upgrade your Swype 
installation, try that.

After I updraded my Swype install everything runs perfectly. Except for my 
Nexus One's trackball dying, but that's not ConnectBot's fault.

Original comment by r...@projectmayhem.co.nz on 3 Jan 2012 at 10:54