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

Anonymous
2012-07-04T04:34:34+00:00

I'm having a problem whenever I try to use contractions that begin with "I" - such as I'm, I'll, etc. When I type "I'm", I get "I'  M" followed by a beep. Same thing with "I'll" - Outlook will type it as "I' L" and beep, not allowing me to enter any new characters until I delete the old and I have to type "I am" or "I will". "I've" is also a problem. It's seems as if the auto spell checker is just choking on any contraction beginning with "I"?

Yes, I am running the latest developer version of Mountain Lion but I've been running it for months with no problems in any Office app. This is something new and totally off the wall.

Any suggestions?

Thanks,

Clinton

Outlook | MacOS | Legacy Outlook for Mac | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2012-07-28T04:59:25+00:00

Final update:

Update to Mavericks to resolve 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.  The fix was released recently in the version of webkit included with Mavericks.

===

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.

Was this answer helpful?

0 comments No comments

90 additional answers

Sort by: Newest
  1. Anonymous
    2013-11-25T19:29:55+00:00

    Mavericks does indeed seem to resolved the issue.  However I’m noticing an odd though less problematic fluke.  With the auto-correct function “capitalize first letters of sentences” re-activated (I had de-activated it as a workaround for the original problem), if the first word of a sentence contains an apostrophe, the auto-correct won’t work and won’t automatically capitalize the first letter of the word.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-11-25T19:17:26+00:00

    Hm. i understand the rationale, mavericks is a free update. 

    unfortunately my up-to-date machine needs quality font management for my trade, and so upgrade is not yet possible.

    Also my older machine is no longer able to update to the latest OS.

    This should be patched by MS. but hey, at least the reply button works again.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-11-25T18:59:24+00:00

    I wonder if anyone's installed Mavericks yet and noted its effect (if any) on this issue.

    Yes.  Update to Mavericks to resolve this issue.  Answer on page 1 has just been updated with this information too for the benefit of others.

    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.  The fix was released recently in the version of webkit included with Mavericks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-10-23T14:44:54+00:00

    I wonder if anyone's installed Mavericks yet and noted its effect (if any) on this issue.

    Was this answer helpful?

    0 comments No comments