Microsoft Word for Mac’s lack of support for LWFN files

Monday, 25 June 2007 @ 12:20

I don’t know if any of you have run across this issue, but I’ve run across a major Microsoft Word for Mac problem. After completing a recent Word update, Word now thinks that all of my fonts with an attached LWFN font file (in other words, all of my Postscript fonts) are corrupt. I can open up Word, but not without hitting the “ok” button a hundred or so times for each time that a dialogue box comes up saying “so and so font is corrupt and should be removed.” Have any of you had this problem? How on earth do you get around it?

respond to post

You must be logged in to post a comment.

responses

  1. wade2007/6/25 @ 12:58

    This isn’t something new. Microsoft Word has done this on Mac OS X for as long as I can remember. There are several problems occurring that I won’t go into detail about that have to do with poor software error handling and not following standard operating system conventions. The only solution that I am aware of is to remove Office from your system and to reinstall.

    To help you more specifically, are the fonts are ones installed by Office or others?

  2. nealjenks2007/6/25 @ 13:10

    These are all fonts that I installed from a Bitstream Library CD, all of which are, I believe, Level I Postscript fonts.

  3. wade2007/6/25 @ 13:14

    Did you install them manually or are you using an application to manage them?

  4. nealjenks2007/6/25 @ 14:08

    I installed them manually.

  5. wade2007/6/25 @ 14:14

    Try putting the in /Library/Fonts instead of ~/Library/Fonts or loading them by means of a font management application and that should remedy the problem. I would recommend using a font management application, such as Font Explorer X, instead of managing them manually anyway. Besides the benefits of not having to manually move files, you will see an increase in system performance as you will only have the fonts you are using loaded.

  6. nealjenks2007/6/26 @ 8:25

    Yeah, I should be using a font manager anyway. Thanks, man. I’ll give it a try.