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-08-02T14:19:42+00:00

    I also noticed this when I installed Mountain Lion.

    It's very annoying. I think I'm just going to turn off auto-correct and let my emails fly with errors.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-07-31T17:59:09+00:00

    I just upgraded last night, and I'm having this problem too. So... what's the solution? I don't want a work-around. I want a solution. Any updates?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-07-30T18:29:44+00:00

    I can also confirm that this is happening.

    The specifics I've seen that may be helpful in solving the issue.

    For me:

    * It only happens when replying to certain emails, not everyone.

    * New messages work fine.

    * It also seems to be dependant on the content of the message I'm replying to, in one specific case I'm having two conversations with the same person, one thread defaults to html in the reply and works fine, the other defaults to plain text has has the issue.

    * When the problem happens, it's not happening for all autocorrects, capitalizing a word at the start of a sentence triggers it, replacing teh with the does not.

    * On an email that I can use to reproduce the issue 100% of the time, it's defaulting to plain text.  Changing it to HTML format does not fix the issue, it is still reproducible 100% of the time, changing it back to plain text, fixes the issue (for that one email).

    * For an email I could reproduce the issue 100% of the time yesterday, I closed Outlook, did a rebuild of the identity, restarted Outlook, and then I could no longer reproduce the issue on that email.  About to try that now with the email today that's causing the issue.  Hmm, rebuilding the identify had no effect this time, the issue still persists on that email.

    Outlook Version: 14.2.3 (120616)

    Mountain Lion Version: OS X 10.8 (12A269)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-07-28T18:06:04+00:00

    I've tested this workaround in creating new mail and replies, HTML and plain text, and so far it appears to have eliminated the problem. Thank you. I will repost to this topic if it arises again with further testing.

    Was this answer helpful?

    0 comments