This is half way between bug report and feature request.
When typing text stored as autotext, prediction doesn't work. For example if pdq stands for 'pretty damn quick', typing odq doesn't bring up a suggestion. If I save pdq to my dictionary, prediction works to find pdq, but still, if I haven't entered the letters perfectly, picking pdq from the list enters pdq rather than 'pretty damn quick'.
autotext prediction
-
- Posts: 5
- Joined: Sun May 15, 2011 2:49 pm
- Phone: Verizon HTC Thunderbolt Froyo 2.2
- cyril
- Developer
- Posts: 2079
- Joined: Tue Feb 02, 2010 4:02 pm
- Phone: Nexus One 2.3
- Location: Nice, France
Re: autotext prediction
You mean "proximity correction" and not "prediction", right?When typing text stored as autotext, prediction doesn't work.
In that case, that's on purpose. Enabling proximity correction for autotext would make predictions completely unusable in some situations, especially if you use a lot of different shortcuts.
Cyril
-
- Posts: 5
- Joined: Sun May 15, 2011 2:49 pm
- Phone: Verizon HTC Thunderbolt Froyo 2.2
Re: autotext prediction
I guess I mean both. Proximity detection and prediction. I don't see why it would be unwieldy to use these features. You will never have near the number of autotext entries as there are English words, so there's no way prediction and proximity detection will be overrun. Maybe have it as an option? If I type pmw instead of omw for "on my way", why can't it proximity suggest "on my way" the way it would if I typed omw correctly?