Download TextExpander 3.2.2. A few specific factors frustrated TextExpander users:
1. TextExpander assumed you were starting a new sentence when switching from one application to another. That is, if you were typing an email, switched to your browser to look up something, then switched back to the email to finish your sentence, the first word typed would be capitalized regardless of its position within a sentence.
2. If you typed a period or other sentence-ending punctuation, then used the mouse to change the position of the insertion cursor, the next word typed would be capitalized regardless of its position within a sentence.
3. Any time you re-positioned the insertion cursor using the arrow keys, TextExpander would not auto-capitalize again until you typed a sentence-ending character.
These issues have been addressed in TextExpander 3.2.2. In applications that thoroughly support Apple’s accessibility interface, TextExpander can now examine the text near the insertion cursor to determine whether the cursor is in a sentence-starting location. Unfortunately, many popular applications do not support this interface, so users of applications such as BBEdit and Microsoft Word users will find that the new version of TextExpander just doesn’t automatically capitalize as often. At least unwanted capitalizations should no longer occur in those applications. Another common case of unwanted capitalization resulted when typing web or email addresses. That is, typing Smile’s web address would result in: www.Smilesoftware.Com with unwanted capital ‘S’ and ‘C’. TextExpander now waits for a space or line break after punctuation before activating automatic capitalization. Additionally, short snippets such as “i “ -> “I “ and “u “ -> “you “ used at the start of a sentence with capitalization enabled resulted in incorrect expansion output which has been fixed.
For the future, a few users have requested that “Eliminate double capitals at sentence start” be changed to “Eliminate double capitals at word start”. That is, it would suppress a second capital letter at the start of a word anywhere. This is helpful to avoid errors like “TRacy” or “NOrth”, but it does replace “OK” with “Ok” (which can be ‘fixed’ with an “OK” -> “OK” snippet). If you have an opinion on this possible future change, let us know your thoughts and reasoning.
