BUG!! Word 2016 fails to print margins correctly / messes up layout (Possible OpenType .otf Font bug)

Anonymous
2015-11-26T19:37:16+00:00

Hallo everyone,

I am having severe problems with Word 2016, as it does not print the document layout correctly as it somehow messes up the margin when printing.

NOTE: This happens when printing to Adobe Acrobat DC and my physical printer!

My document layout:

• no markup,

• custom margins (set to 1,27cm top / bottom and left / right - my printer can easily handle these...)

• no header or footer

• paper size set to A4 in all settings

IMAGE 1

The following is picture shows page 1 of my document in "Print Layout"-view. This is how I want the document to look when printed.

IMAGE 2

Here is a picture of the Print-preview menu. You can see that the Print preview still shows the document exactly as I want it. No problems. No funny settings selected. No "Print Markup" selected.

IMAGE 3

Now this is what happens when I print the actual document:

The bottom margin changes and suddenly the whole layout is messed up!

Please advise whether this a bug, or some setting I seem to wrongfully configure.

This is really annoying as I sometimes spend hours to get the layout and spacing in a document right, but then when it comes to printing the document, everything is messed up.

Thank you.

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

138 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-04-29T07:09:54+00:00

    Hi Zoey,

    Thanks for popping in here.

    Yes, the issue is still there on win10/Office365 and an OTF font.

    The trick of creating a macro described in a reply in this thread has been working ok so far for me:

         ActiveDocument.SetCompatibilityMode 14

         ActiveDocument.Compatibility(wdUsePrinterMetrics) = True

    But this is painful to systematically have to launch a macro to have a proper WYSIWYG experience on MsWord.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-04-29T03:52:52+00:00

    I still am experiencing the issue. I did notice that Adobe provides a newer version of a.o. Minion Pro via Typekit and I installed (I have a Adobe CC subscription) but the problem persists.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-04-28T23:42:58+00:00

    Hi Lubbzter,

    My name is Zoey, and I am a member of the Word team. We previously fixed an issue related to .otf font. I would like to follow up and see if you are still experiencing the issue.

    Thanks,

    Zoey

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-04-06T18:46:55+00:00

    I'm having the same issue. Why no updates is STILL provided????

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-03-21T18:24:31+00:00

    I share your frustration Matthew! I too have been having similar repeatable problems with Word, and have not been able to find out how to get someone at Microsoft look at it seriously.

    My problem is that Word indexes and ToCs are reporting incorrect page numbers  — but only when the document uses an OpenType CFF font (Adobe Garamond Pro, Minion Pro). If I change the document to an OpenType TT font like Times New Roman or Segoe UI, the rebuilt index and ToC reports correct page numbers. (See my detailed Office TechCenter post here.)

    I think that feedback I received about this problem on an Adobe support forum (here) may be related to the problem we are both encountering:

    Adobe Garamond Pro and Minion Pro are both OpenType CFF font families. Times New Roman and Segoe are both OpenType TrueType font families.

    The primary difference between the OpenType CFF and OpenType TrueType fonts is the outlines and hinting technology used by the font.

    OpenType CFF uses the same Bezier curve and hinting mechanism used by the original Type 1 fonts used in the original PostScript printers and use a coordinate system based on 1000.

    OpenType TrueType uses the quadratic curves and programmatic hinting mechanism used by TrueType fonts, using a coordinate system based on 2048.

    I am wondering whether Word is doing something that assumes that 2048 value (it shouldn't) for font character widths being based on. It is crazy enough to actually be the issue and about the only thing that I can think of that just might be the root of the problem.

    This seems to fit the behavior we are seeing, and certainly suggests a bug. I do hope that a Microsoft Office technical person sees this thread so it can be investigated and resolved quickly.

    (If it will help, I can provide a document that exhibits this problem so it can be examined.)

    Was this answer helpful?

    0 comments