Problems when using contractions such as I'm, I'll, etc. Any help?

I did go into Preferences/AutoCorrect/Exceptions and just added in:

's

't

'l

Seems to have fixed the problem.  One thing.   When typed into the exception bucket, it seems not display right ('s shows as s.) but it works.

A leaner solution:

Get to the same Autocorrect section of the preferences dialog. (CMD+,)

Click "Exceptions"

Click the "First Letter" tab up top.

Click the "+" sign on the bottom, and add I' to the list.

When I tried adding the I with an apostrophe it returned an error.  But I found an alternative!

Go to Edit -> Substitutions -> Show Substitutions to bring up the Substitutions dialogue box. 

Make sure 'Text Replacement' is ticked and click the Text Preferences... button.  This brings up the Language and Text dialogue box from System Preferences with the text page selected.  (NB you could probably just go here by clicking the Apple -> System Preferences -> Language & Text.)

Be sure 'Use symbol and text substitution' is ticked and add the offending words to the 'Replace' column and the desired corrections to the 'With' column.

Replace | With

I'D | I'd

I'M | I'm

I'Ll | I'll

Close and test.

OSX v10.8.3

Outlook 14.3.2

Thanks for informing that this is a Webkit regression bug, that explains and helps a lot.

However, I find the solution of unchecking Autocorrect's "Capitalize First Letter of Sentences" to be a little heavy-handed.  Sometimes when scrawling out emails, I appreciate the capitalization help.

An alternate solution to this exact error of caps after I' such as in "I'd, I'm, and I'll,"  I have a leaner solution:

Get to the same Autocorrect section of the preferences dialog. (CMD+,)

Click "Exceptions"

Click the "First Letter" tab up top.

Click the "+" sign on the bottom, and add I' to the list.

When you close this, you'll have added the case of I' to items for which you don't want the succeeding letter to be capitalized.  Simply put, I'd, I'm and I'll will all type properly now, and won't yield I'D, I'M and the nightmarish I'Ll.

Thanks!

Dear Scott,

I know it's an old thread for you, but for me the problem is new and restricted entirely to Entourage 2008 with my own User ID. Just wanted to say, I don't think it's purely a webkit problem - in a different test user set up there is no problem with the capitalization of just one letter ("M") after an apostrophe. All the workarounds and instructions for switching preferences on and off, changing autocorrect etc don't work. I get the feeling it is some sort of autocorrect that is invisible to me that's causing it in my main user ID. Would it be possible to make a comprehensive checklist of all the parts of the system and apps where auto-corrections might have been set - so I can systematically eliminate them all?

               

As a temporary workaround please turn off the "Capitalize first letter of sentences" autocorrect setting.

 

Select the menu Outlook, Preferences, Autocorrect and uncheck "Capitalize first letter of sentences".

===

 

Update:

The recent Mac Office 14.2.5 release did not contain a fix for this issue.

 

The problem is related to webkit.  Webkit is a component of OS X (it is the HTML rendering engine behind Safari).  The bug was reported to Apple shortly after this thread started and we are eagerly waiting on a fix.

 

Apple released version 6.0.2 of Safari early November 2012, including a webkit update.  It is that update which is causing people to see changed, but not fixed, behavior.

 

The particular test case I have been using to reproduce the problem still fails with Safari 6.0.2.  Other uses are reporting that situations which were broken before now work.

 

There is no benefit in trying new identities or new user accounts.  The issue is well understood as being a webkit regression from when Mountain Lion was released.  It is not related to any problem with your identity, account or installation.

 

The above temporary workaround is still the only solution to suppress the problem until a complete webkit fix is released.  Updating to Safari 6.0.2 through Apple Software update may address some situations.