Word 2016 fails to print margins correctly / messes up layout (Possible OpenType .otf Font bug)
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
When I changed the fonts to Arial, the PDF printed correctly!
The 2 custom fonts I used, are both .otf
Both of these are high quality commercial fonts.
I've never had a problem with regards to spacing, margins and layout using these custom fonts in earlier editions of Word or other software applications (used them in Excel 2016 and Photoshop CC 2015).
Thanks for reporting this! Just a note to let you know that we’re working on it.
Support "MinionPro" PLEASE!!! commented
Word 2016 does not correctly support OpenType CFF fonts (e.g., Adobe Garamond Pro, Minion Pro):
Adobe Garamond Pro and Minion Pro are both OpenType CFF font families (whereas, for instance, Times New Roman and Segoe both belong to OpenType TrueType font families and do not give any layout/printing prolems).
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.
Word 2016 is probably doing something that assumes that 2048 value (it shouldn't) for font character widths being based on.
I share the general frustration. Minion Pro is this charity's standard font for newsletters and even now after all the complaints below it still won't print properly or publish as a pdf. Microsoft is too clever by half; i.e. can't leave well alone.
Also having this problem - saving as a PDF turns a one page document into two pages. Saving in compatibility mode did not fix. Changing font does - but need to use the font required by the customer.
Emily Klein commented
I started having this issue with Word 2016 today; the solution at the link above (putting the document into Compatibility mode based on Word 2010) did work for me. Now ask me how much time I wasted trying to do something that I was able to do yesterday without any fuss...
The newest KB that claims to fix this DOES NOT!
Please, this is urgent!!!!
Eric Fletcher commented
I too am having related problems. Index and TOC page numbers are being reported incorrectly ONLY when OpenType CFF fonts (like Adobe Garamond Pro and Minion Pro) are being used. If I change the document's fonts to an OpenType TT font (like Times New Roman or Segoe UI), the page numbers are reported correctly. (Word 365 version 1702, build 7870.2024)
Having this same line spacing issue. Document works and prints as it should in 2016 Mac version, but not on 2016 PC version.
Had to switch to win 2013 and make a few edits with the spacing. After that, it printed correctly. Microsoft owes me 3 hours of pay.
Having same issue. Happens if I use fonts that have "Adobe" in the name. Seems to happen when I use textboxes in a document.
PLEASE FIX commented
The wrong handling of fonts in Word 2016 (in my case Minion Pro), resulting in totally changed layout when printing a hard-copy or to PDF, is unacceptable and a MAJOR bug that needs to be fixed ASAP!!!
Our company depends on this!!!
Has anyone heard any updates? I've tried removing hidden text, I've tried converting from otf to ttf fonts, and anything else I've seen suggested. The number of pages in print preview is 30 pages less than show up in the pdf.
1. I think this issue is more of a line spacing (or font metric) issue than a margin issue.
2. Yes, this issue is a major bug and drives me crazy also, Word is no longer WYSWYG. I might as well be using Tex.... (at least over there bugs get fixed)
It's very disappointing that major bugs can go reported for over a year without Microsoft doing anything about it.
I wish that I knew the magic word that will make Microsoft react and fix it (any ideas anyone how to turn this into a security vulnerability? Irate user don't bode too well for security either :-).
Still have the same issue with Word 2016 version 16.0.6925.1049 from Office 365 pro plus
I had to open in 2013 and then fix it there and print.
If I then open the file again in Word 2016 the formatting looks all over the place but prints correctly
Nice work Microsoft
Surely this should be fixed by now, OTF fonts fail to print out accurately as per the original file and Print Preview in Word 16 (with Windows 10)
I have had this issue as well for OTF fonts (Gotham, Adobe Garamond Pro, Sabon, etc.). It seems to be fixed when converting the fonts to TTF format.
Also having this problem when using OTF font 'Fanwood'. Please advise when this will be fixed.
I am having a problem with Word 2016 (with Windows 10) in that pages in Print Preview print out differently, with text over-running onto other pages, and I can only print reliably if I either enter page breaks at the end of each page, or change the font from OTF (Optima Light) to a TTF, whereupon it works.
I'd like to update my comment - seems I can't edit - to report that I am on Version 1609 (Build 7369.2038) and it doesn't matter if I print to either of my two external printers (inkjet or laser) but the issue happens on print to Adobe .pdf as well
I too am having this problem! I'm running Windows 10 Professional, the latest update of Office 365 64 bit. My document has custom open type font - Frutiger. Every year I publish an annual report in which many high resolution pictures and graphics are laid out carefully on each page. This year, on the latest version of Office I am having random layout issues and so far technical support on my Office 365 Business account for this issue has been completely ineffective and unhelpful
I am having this except same problem with documents in Garamond.