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 No comments

138 answers

Sort by: Newest
  1. 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 No comments
  2. Anonymous
    2017-03-09T05:05:25+00:00

    Thanks for all the options but unfortunately we have over 1500 users that are experiencing the issue. We use an OpenType Font and it is mandated by our Style guide so we are not able to just use something else.

    Moved from older office versions to Office365 and Office2016 and there is no chance of winding back now.

    I hope the answer can come quickly as I dont think all the students and staff can adjust or insert the vba option previously mentioned.

    Thanks in advance 

    Matthew

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-03-01T15:06:41+00:00

    I have a customer with the same problem. I have added a VBA macro for the time being which then let's the user see the actual WYSIWYG format in their chosen font, whereby they then trim the spaces etc. to get the correct formatting. After that when they print, the preview is correct and it prints correctly. It is when the actual rendering is output to the printer that the disparity appears.

    I got this from another thread on the subject. Many people have the same problem and even after updating Office it still remains.

    ActiveDocument.SetCompatibilityMode 14

    ActiveDocument.Compatibility(wdUsePrinterMetrics) = True

    Source: https://word.uservoice.com/forums/304924-word-for-windows-desktop-application/suggestions/10992303-word-2016-fails-to-print-margins-correctly-messe?page=1&per\_page=20

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Suzanne S Barnhill 279.1K Reputation points MVP Volunteer Moderator
    2017-02-28T03:39:45+00:00

    I'm glad you found my answer helpful.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-02-27T17:33:36+00:00

    Dear Suzanne,

    I have been struggling with this issue for several hours. And then finally I came across your helpful answer. Worked like a charm! Thank you - Thank you - Thank you!

    Signed,

    A very grateful Word nerd

    Was this answer helpful?

    0 comments No comments