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-09-15T22:14:15+00:00

    Rather than trash plist files, it's easier to check in a new User first with all new preferences to see if this fixes the problem.

    Testing in a new User will quickly tell you if the problem is system wide or if it's your User's folder that contains the problem.

    CREATE A NEW USER

    Go to System Preferences --> Create a New User in Accounts. Switch to the New User by logging out/in or use Fast User Switching.

    Open Office app for testing. It won’t be in the Dock in the new User. Go to Applications to open.

    Do you still see the issue?

        If yes, then the problem is with your base files.

        If no, then the problem is in your User's folder.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-09-13T23:24:49+00:00

    As I wrote before, I found that there was a glitch hidden somewhere in the preferences (.plist) for Entourage that was causing the problem. All the solutions discussed before are work-arounds that help if you haven't managed to layer the problems too much with the electronic form of Band-Aid/sticky plaster in your attempts to solve the issue. Using autocorrect etc only works up to a point - you can sometimes end up with conflicts arising from too many auto-correcting corrections so to speak.

    Best thing to try, worked for me 100%, and will refresh things anyway, is to throw away the preference files for Entourage, and maybe even Word and PowerPoint if things are really bad - then clean out your caches with something like Onyx. Throwing out preferences is a bit like starting your Office apps with a fresh slate. Doesn't damage anything, though it might be irritating if your frequently used corrections and set ups have to be installed again, but nothing as irritating as the problems everyone above has encountered.

    So - my advice is to go user name/library/preferences….then scroll to the batch that starts with "com.microsoft…….." then throw out the Office Apps ones that end with " .plist " (this might look like gobbledegook, but if you navigate your way to the contents of the preferences folder, it'll all become clearer). If your problem is mild, you might solve it with just throwing out Entourage/Outlook or whichever app you are having problems with. The dramatic version of this is to take out anything that is a Microsoft programme .plist  (don't forget to store them in a folder, on your desktop rather in the trash so you can put everything back if it all goes pear-shaped). After removing the plists, restart the computer so that the new plists are built back, and you have a good chance of everything working properlyagain. I had persistent problems with "I'm" too and this managed to clear it.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-09-12T20:21:16+00:00

    Only Microsoft can give you a real solution. We are users just like you.

    http://www.microsoft.com/mac/product-feedback

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-09-12T14:43:32+00:00

    This is absolutely insane. Every time I attempt to type I'm it gets changed to I'M. Tried the solution in Autocorrect settings, but when I try to enter the apostrophe as an exception, it automatically adds a period to the end and doesn't work!!!!

    You've got to be kidding me, right? A contraction as common as "I'm" is not recognized?!

    Please give us a real solution, not a work around.

    This is way too common and obvious to not have been addressed.

    Was this answer helpful?

    0 comments No comments