Windows 10 - Helvitica Font Issue

I have never encountered this problem before, so I don't have a pat solution and I am not versed on how 7 and 10 differ (if any) in the way they render a print. However, a simple experiment that might provide a solution is to delete the Helvetica files from the Win 10 machine (after backing them up of course) and then copy the Helvetica files from the Win 7 machine.

I don't see it much anymore, but back in the early days of Acrobat, printing could be fouled up by someone having the exact same font from the same publisher, but a different version number.

That may not be the problem, but it's a relatively easy test in order to rule it out as a cause.

The Helvetica TTF font will need to be installed within Windows 10 OS.

MS has done away with Helvetica and subs Arial for it whenever Helvetica is called. This happens at the Windows OS level and doesn’t just apply to Microsoft Office. The behavior has been set all the way down in the Windows Registry:

 HCLM/SOFTWARE/Microsoft/Windows/NT/CurrentVersion/FontSubstitutes which lists the substitutions.

InDesign should export a Fonts folder along with the .IND file that contains all of the fonts being used in the document.

This would explain why InDesign application can print the file with fonts, where as the Windows 10 OS cannot.

Sorry for the delay. My users were printing from InDesign to a Konica MFP. After the font issue arose we also discovered color match issues between the two on the fonts and graphics that did print. After reloading the fonts and not solving the problem I contacted our Konica maintenance rep who advised us to switch to PCL drivers instead of the Postscript. That resolved both our font and color issues.

Ok, but I am not sure that using a PCL driver to print out of InDesign is the best way to manage color or fonts. Your designers are not really looking at the actual color settings applied within InDesign. You really need to use the PostScript driver to get accurate color.

Here is why. PCL is device dependent. This means that the drivers for this language utilize the printer hardware for creating some of the printed data, usually graphics data such as fill areas, underlines or fonts. Individual printers may perform these tasks differently giving you a slightly different output.

Unlike PCL, PostScript is device independent. This means that the PostScript language creates all of the print data and does not rely on the printer for print data. This allows the output to be consistent when printed on more than one type of printer or print device or sending out to a printing company for further production.

I do realize that but both the current and updated postscript Konica drivers had the same issue. This is only a temporary solution until I can get new functional postscript drivers from Konica.

What device are you printing to? I run mostly Mac (design stations) but had similar issues with both the C6000 and 1060L v1 drivers.

Make sure the driver matches the firmware on the printer. If it is a Fiery you should be able to download the driver directly off of the printer's web interface.

We are printing to a konica Bizhub C754 without the Fiery option. My users are satisfied with their printed outputs at this time. We will continue to use the PCL drivers until working postscript drivers are available. We do have a service vendor also working the issue with Konica.