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
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

90 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2012-10-12T11:05:38+00:00

    For me:

    1. Only replies. New messages are fine for me.
    2. Plain text (replies) only. HTML is fine for me.
    3. For any reply to a plain text message. No special steps.
    4. I was using the default AutoCorrect settings. I've since turned off the auto-capitals at the beginning of sentences and that work-around has been successful.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-10-05T07:03:05+00:00

    This happens on every plain text e-mail I write. For me, that has only been replies to plain text e-mails as I always write new e-mails in HTML. If I switch the e-mail to HTML, the problem goes away. So, this is purely limited to plain text e-mails in my case.

    I've never played with the auto-correct or auto-format options in Outlook. I don't remember doing anything of particular interest in Safari.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-10-02T18:22:18+00:00

    I just googled this issue and have been scrolling through, my issue is the exact issue as John's.

    New MacBook Air, haven't loaded any new fonts yet either.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-09-22T16:50:31+00:00

    The problem is related to webkit and composing. A webkit API that we use to implement Office autocorrect, moveWordBackward, broke in the version of webkit that Mountain Lion shipped with. This has also appeared in a software update for Lion users.

    The bug was reported to Apple shortly after this thread started and we're eagerly waiting on a fix.

    Starting with a clean user's folder won't help this problem. The temporary workaround that is currently marked as an answer for this thread is the only option to avoid the problem until a webkit fix is released.

    Was this answer helpful?

    0 comments