Font printing errors

[stridemat]

When printing documents with a certain font (Kalinga) the attached happens. This happens system wide and on both the printers in the office. If I open the same document from my iPhone or iPad and print via AirPrint then these artefacts disappear. Likewise if I print to Adobe Acrobat Reader and then print to the actual printer from within Adobe then these artefacts also disappear.



Strange one I know, but it is quite frustrating. Anyone any ideas? Im using a 2013 MBA with all the latest updates installed.

 

[AlanShutko]

What program are you printing from?

 

[stridemat]

What program are you printing from?

Any OS X Programme or Microsoft Office. The only programme that seems to work is Adobe Acrobat Reader as this has its own printer renderer.

If I upload the font in question, would you be able to install it on your system and try to print something in Kalinga? The problem letters appear to be W and X.

 

[AlanShutko]

If I upload the font in question, would you be able to install it on your system and try to print something in Kalinga? The problem letters appear to be W and X.

Sure, I can do that. I suspect that the font is malformed in some way, and the printer's rendering engine doesn't like it. You don't happen to be printing to postscript printers, do you?

 

[stridemat]

Sure, I can do that. I suspect that the font is malformed in some way, and the printer's rendering engine doesn't like it. You don't happen to be printing to postscript printers, do you?

Thanks. Font can be downloaded from removed (I will delete in a day or so). If you can install and then try to print something in the Kalinga font with numerous W's and x's.

 

[AlanShutko]

Well, I printed it to an HP LJ2100M, a postscript printer about fifteen years old, and it was fine when I printed as PostScript, but had the same problems you saw when I printed as PCL.

I did a little looking, and found another post that indicated problems rendering Kalinga in prepress. This is suggesting to me that there are problems in the font geometry which break some rendering engines but not others. I checked with frontline, and it complains of the following:

ERROR      2 Self-intersecting glyph
ERROR      5 Missing points at extrema
ERROR      9 Bad glyph name

If you can, it might be a good idea to use a different font, but if you need Kalinga's Oriya support that might be difficult. Maybe use some complementary sans font for roman text and Kalinga for Oriya?

You might check if there is a newer version of the font available from Microsoft. The version you have seemed to come with Windows 8.1, so Windows 10 might have a newer version (but I don't have Windows 10 handy).

Monotype licenses the fonts for Microsoft, so you might check with them to see if there is a newer version available somehow, or a way to get in touch with Microsoft Typography.

 

[stridemat]

Well, I printed it to an HP LJ2100M, a postscript printer about fifteen years old, and it was fine when I printed as PostScript, but had the same problems you saw when I printed as PCL.

I did a little looking, and found another post that indicated problems rendering Kalinga in prepress. This is suggesting to me that there are problems in the font geometry which break some rendering engines but not others. I checked with frontline, and it complains of the following:

ERROR      2 Self-intersecting glyph
ERROR      5 Missing points at extrema
ERROR      9 Bad glyph name

If you can, it might be a good idea to use a different font, but if you need Kalinga's Oriya support that might be difficult. Maybe use some complementary sans font for roman text and Kalinga for Oriya?

You might check if there is a newer version of the font available from Microsoft. The version you have seemed to come with Windows 8.1, so Windows 10 might have a newer version (but I don't have Windows 10 handy).

Monotype licenses the fonts for Microsoft, so you might check with them to see if there is a newer version available somehow, or a way to get in touch with Microsoft Typography.

Thanks. I have contacted Monotype to establish what version they have available on their store.

 

[vexorg]

What happens if you save it as PDF?

 

[stridemat]

What happens if you save it as PDF?

It looks fine on the screen, but when printing the same issue occurs.

 

[vexorg]

Strange, never had a PDF have a problem between screen and printing the PDF