Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Some Google fonts print incorrectly on anisotropic RIPs #1370
Does anyone have any insight into why some google fonts print distorted when a RIP using unequal resolutions? We have designers and laypersons sending in PDF's using free Google fonts for book production. Most of our work isn't proofed before printing so if the printer doesn't notice we potentially have a pallet of paper destined for the trash. This problem has only been apparent for the last couple of years and I have no way of knowing that the font is going to be a problem.
@Buckers66 this is really hard to analyze or debug. We need much more information to even get started.
A list of fonts that trigger the issue as well as fonts that don't would be a good start. Best if all fonts are in Google fonts, if possible, because we have access to them and, can look into them and compare. Not all of our fonts are made the same, so it would be strange if really all trigger the issue. (Maybe all that use ttfautohint do, or something like that.)
Then, we need a reproducible example of your issue. That way, when fixed, we can't reproduce it anymore and then we know we're good. This is however really hard, because we don't have access to a SCREEN Truepress jet520. Is there a way for you to get a PDF or bitmap image proof from the RIP, without printing it? One that displays the behavior? That way a developer could send you pdfs and you could send back proofs.
Did you try to contact the company "SCREEN"? Maybe it's an issue with their software. Maybe we can find out what software they use as a RIP and use it ourselves directly. It's also possible that there is a bug in the RIP, not in our fonts. I'm sure SCREEN would be interested to get this sorted out as much as we do.
Hi, Thanks for the prompt response although mine wasn't as I got rather busy the last few days. First of all here is my current but ever expanding list of fonts that are not printing correctly on this device:
There is one other font that is not a google font we discovered in 2011:
We contacted SCREEN about this issue who in turn contacted ADOBE and here is their responses to the small "a" problem:
_FROM SCREEN JAPAN:
This font is embedded in the PDF. Therefore, the font WAS NOT substituted in SV-110. The font was a True type font.
The file contains TrueType fonts which are being ripped at anisotropic resolution of 720x360. TrueType fonts can have size dependent instructions.
TrueType fonts can have instructions that test for anisotropic scaling and change their instruction processing sequence accordingly. Since this is an uncommon rendering mode, some fonts exhibit bugs that are only triggered under these circumstances.
The issues demonstrated with this bug submission reflect defects in the font program, not in the font processing software.
Using TrueType fonts with anisotropic transforms is generally problematic.
This is not a CPSI issue, these kind of problems can arise with some TrueType fonts, if you try to render them at anisotropic resolutions e.g. 720x360. We have seen these kind of problems in past, these are TrueType Font issues._
In regards testing fonts, there is no access to this RIP without printing onto paper, there is a low res RIP feature but it is only in non isotropic resolution eg 72 x 72 dpi so will not reproduce the error. I will however print test samples if anyone on this forum wants to test a corrected font.
Very interesting. Many of my own teams use Google Fonts for print, we never experienced any problems (but we don't use anisotropic RIPs).
Some fonts mentionned exist in TTF and OTF (CFF) format. It might be useful to compare tests:
thlinard: Thanks for that suggestion, the OTF versions of those fonts print perfectly. On the flipside I had probably the worst example of my troubles printing this morning with 18 fonts behaving badly. All the fonts in the book were TT, the list of fonts in the publication are here and I've put the word (faulted) next to the troublesome fonts. If someone could compare the structure of the problematic fonts with the structure of another font in the list that didnt cause any issues I would be most appreciative:
added this to the Bugs in Font Files 00 Resolution Effort Undetermined milestone
Dec 8, 2017
I did some research, and the printing problems aren't new:
About Lato, Adam Twardoch commented: "I did hear of printing problems, even with the most current version, which most likely are related to hinting and ttfautohint — but it's next to impossible to debug those problems"
I looked at the Truepress Jet520 specifications, and the printer have two isotropic resolutions:
So, for a short-term resolution, perhaps you can:
For long-term resolution, the problem lies probably in a common production tool (
I think I have a problem related or equal to the OP.
As you can see, Dosis (used for the titles) works fine, Lato does not.
As far I can tell this won't affect a big group of users, but since some of our clients started complaining, I need to solve this. For now, I'm going for the self-hosted option but being able to use google fonts would be much easier!
@webberig turns out it could have been caused by two different things:
I have this issue during print preview of my page and when saving via .pdf.
I've isolated the issue to "font-style: italics" CSS to be the problem.