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
    2012-08-09T14:41:42+00:00

    I'm having the same issue as CerebralGardens described it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-08-08T18:14:56+00:00

    I am also having this issue.  It happens on all emails, regardless of wether I am creating a new email or responding to one.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-08-07T04:31:04+00:00

    Same Problem here.  I just updated MS Office 2012 and installed Mountain Lion.  Only some emails are effected, and hitting undo fixes the weirdness so I can continue typing, so it looks like some sort of autocorrect or special character (or language) bug.  I hope someone solves this soon.  It's really annoying.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2012-08-03T21:04:47+00:00

    I'm experiencing this problem as well.

    It seems to only happen with plain text and only when the message starts out as plain text. If your default message format is HTML and then switch to plain text, you will not encounter the problem.

    You'll also see this if your default message format is HTML, but also have the "When replying or forwarding, use the format of the original message" preference checked and the message you are replying to or forwarding is plain text.

    Unchecking the "Capitalize first letter of sentences" preference works around this problem for now.

    Was this answer helpful?

    0 comments No comments