Word 2010 problem with PostScript Type 1 fonts and PDF export

Anonymous
2010-06-18T19:07:47+00:00

I have been using Office 2010 since the Beta period and I am now using the release build.

I use Adobe Postscript Type 1 fonts regularly in my documents, and I have found that Word 2010 (and presumably all of the Office 2010 applications) has several problems working with PostScript fonts.

Most notably, the "Save as PDF" function will create documents with an odd gradient effect applied to all PostScript fonts.

Secondarily, the Word editor frequently glitches and renders PostScript fonts using a sans-serif font that looks to be Arial.

The following are a demonstration of the issue:

![](http://www.tsotech.com/images/office2010/original-doc-small.jpg)

This is an original document typed in Minion, an Adobe PostScript Type 1 font.

![](http://www.tsotech.com/images/office2010/pdf-version-small.jpg)

This is the document as rendered by muPDF, a very lightweight PDF reader.  Note that the official Adobe Acrobat Reader will render the document correctly.  I suspect Microsoft only tested the PDF export functionality with the Adobe Reader and concluded that it was functioning correctly.  But please note that alternative readers are fairly commonplace, especially with so many security issues being found daily in Adobe's products.

![](http://www.tsotech.com/images/office2010/mac-small.jpg)

I don't have access to a Mac, but the above screenshot was from a Mac's PDF reader attempting to display a different PDF document I had sent a colleague.

Finally, during regular use of Word 2010, the editor will fail to render PostScript Type 1 fonts correctly, falling back on a sens-serif font that I believe to be Arial.  See below:

![](http://www.tsotech.com/images/office2010/display-glitch-small.jpg)

Please investigate these issues, Microsoft!

Microsoft 365 and Office | Word | For home | Windows

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
2010-09-09T05:13:08+00:00

There are 4 issues in this thread for Word 2010 RTM:

  1. Some PostScript fonts display incorrectly after being edited in Word's Print Layout.
  2. Documents with some (but not all) fonts containing PostScript outline data (Ex: Helvetica, Times) crash on open.
  3. Documents using fonts with PostScript Outline data saved as a PDF in Word render correctly in Adobe Reader but incorrectly in some other PDF Viewers.
  4. Documents using fonts with PostScript outline data saved as a PDF in Word render the text as a static image rather than selectable text.

Issue #1

To assist us in solving this issue, please answer the following questions. Thank you.

  1. What is the full name for the printers you have installed? Which of these is the default printer? [Start -> Type "Devices and Printers"]
  2. What editing languages do you have enabled in Word? [Open Word -> File -> Options -> Language]
  3. When in a corrupt state, does changing to a different printer (and back) fix the issue? [File -> Print]
  4. Can you reproduce the issue in *.doc files? [File -> Save As -> Save as type = "Word 97-2003 Document (*.doc)"]
  5. Can you reproduce the issue in *.docx files?  [File -> Save As -> Save as type = "Word Document (*.docx)"]
  6. Can you reproduce the issue in Draft View? [View ->Draft View]
  7. Can you reproduce the issue in both Portrait and Landscape orientations? [Page Layout -> Orientation]
  8. Can you reproduce the issue in a version of Windows earlier than Windows 7 / Windows 2008?
  9. Can you reproduce the issue in a version of Word earlier than Word 2010?

 ===

Here are several workarounds for this issue from my other thread, but please continue to assist us by answering the questions above. Workarounds in order of most convenient to least convenient are:

  1. Add a Right-to-Left language, such as Hindi, to your list of editing languages. [(In Word) File -> Options -> Language -> [Add aditional editing languages] -> Hindi -> Add]
  2. Each time a document is opened with the incorrect font being displayed change to a different printer (and back). [(In Word) File -> Print]
  3. Uninstall all printers from Windows. [(In Windows) Start -> Devices and Printers]

Issue #2

Problem A – Use one of these workarounds if you are crashing when opening documents with fonts Helvetica or Times.

  • Remove offending PostScript font substitutions from the registry location. Restart computer.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]

  • Install the OpenType versions of the offending PostScript fonts.
  • Uninstall the offending PostScript fonts.
  • Open the Font Dialog Box (Ctrl + D) before attempting to display an offending PostScript font. This fix lasts until Word is closed.

Problem B – Use one of these workarounds if you are crashing when opening documents with fonts other than Helvetica or Times. In this case you are most likely crashing due to your printer driver.

  • Change your default printer to another printer that does not crash (ex: Microsoft XPS Document Writer).
  • Uninstall your printer (or all printers).

Issue #3

Currently the best workaround is the one already given by the original poster: Open your PDF documents in Adobe Reader rather than muPDF or the Mac's default PDF reader.

Issue #4

When saving documents using fonts with PostScript outline data, Word 2010 only supports outputting the text as a static image, and does not support outputting the text as selectable text. Currently the best workaround is the one already given by the original poster: Use a printer driver that outputs to PDF such as Adobe Acrobat or CutePDF.

-Omega

Was this answer helpful?

1 person found this answer helpful.
0 comments

61 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2010-09-03T04:26:07+00:00

    All:

    MSFT tech support has closed the incident.  They'll re-open and deal with it ONLY IF someone can describe a repeatable scenario for reproduction -- in this case, this means a PC configuration that yields the problem.  See above, can someone help out? 

    Yuck, I am disappointed in Microsoft's response to this.  I understand their need to be able to replicate this, but judging by the number of people who have reported issues with Type 1 fonts, I doubt that there should be any difficulty for them to replicate this within their test farm.

    I don't have the time necessarily to reinstall my applications either, and I doubt that it would change the behavior of anything in any case.

    This problem has kept me clinging desperately to my Office 2010 Beta installations that I have on my other two machines.  The problem doesn't exist in Office 2010 Beta, so I can use those and continue to be productive.  Like you, I only have one machine affected by this and unfortunately it's my primary machine, on which I elected to install the release version of Office 2010.

    Does anyone know when the Beta is time-bombed to stop working?  I fear it's imminent and I'll suddenly find myself hosed by this Type 1 font problem on all of my machines.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-09-02T07:59:26+00:00

    My Client configuration has Windows7 32bit, Office2010 and Helvetica Type1-Font installed.

    In Word2010 when I write text and format the text with the Helvetiva Type-1-Font then Word2010 crashes.

    Now I have found out when I first open the Options-Page inside Word2010, in there in the Advanced-Tab I click on the Font Substituten-Button. Then I receive the answer no Fonts subsitution is necessary.

    No I open a blank document, write my text, and then I fornmat the text with the Helvetica Type1-Font, and...no crash. I can save my document and reopen it without problem.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-09-01T22:08:46+00:00

    After finally running out of patience, I've initiated an official support request with Microsoft on this problem.  So far I've been impressed with their responsiveness, hopefully they'll admit this is a problem "soon".  I'll update on this thread.

    Thanks for escalating this, Adam.  Any news from Microsoft yet?

    ARGH.

    It seems that Microsoft's position is that until andunless the first-level Word tech support can duplicate the problem on a (virtual) machine, there's nothing that can be done.  I've spent a fair amount of time trying things, but (1) though I have been able teo find a easy, simple, consistent reproduction scenario (on my machine), (2) have been unable to come up with a way for MSFT first-level support to see the problem happen. 

    The more I mess with this, the more convinced that this is certainly a Word bug, but simply can't get past the Word firewall "If I can't make it happen here, there's nothing we can do."

    I have one PC with the problem, one without.  Unfortunately, the one with the problem is my main PC (and the one that generates the bulk of my revenue).  I could take a day or two and reinstall everything (taking good notes), which may yield a PC that has the problem... but frankly I'm not entirely sure if I can spare the time.

    Does anyone out there care enough about this problem to help me out?  I've spent a great amount of time getting nowhere, and the only path forward seems to be one that'll take another 'bunch' of time.  Can someone start from scratch, a complete reinstall, and take very good notes about what was installed/updated in what order that yields a computer with the problem?

    Otherwise, I'm not sure we'll ever get anywhere.

    Adam

    All:

    MSFT tech support has closed the incident.  They'll re-open and deal with it ONLY IF someone can describe a repeatable scenario for reproduction -- in this case, this means a PC configuration that yields the problem.  See above, can someone help out?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-08-31T22:39:24+00:00

    After finally running out of patience, I've initiated an official support request with Microsoft on this problem.  So far I've been impressed with their responsiveness, hopefully they'll admit this is a problem "soon".  I'll update on this thread.

    Thanks for escalating this, Adam.  Any news from Microsoft yet?

    ARGH.

    It seems that Microsoft's position is that until andunless the first-level Word tech support can duplicate the problem on a (virtual) machine, there's nothing that can be done.  I've spent a fair amount of time trying things, but (1) though I have been able teo find a easy, simple, consistent reproduction scenario (on my machine), (2) have been unable to come up with a way for MSFT first-level support to see the problem happen. 

    The more I mess with this, the more convinced that this is certainly a Word bug, but simply can't get past the Word firewall "If I can't make it happen here, there's nothing we can do."

    I have one PC with the problem, one without.  Unfortunately, the one with the problem is my main PC (and the one that generates the bulk of my revenue).  I could take a day or two and reinstall everything (taking good notes), which may yield a PC that has the problem... but frankly I'm not entirely sure if I can spare the time.

    Does anyone out there care enough about this problem to help me out?  I've spent a great amount of time getting nowhere, and the only path forward seems to be one that'll take another 'bunch' of time.  Can someone start from scratch, a complete reinstall, and take very good notes about what was installed/updated in what order that yields a computer with the problem?

    Otherwise, I'm not sure we'll ever get anywhere.

    Adam

    Was this answer helpful?

    0 comments