InQuestion: Solving Cross-Platform Font Problems
This article appeared in Issue 115 of InDesign Magazine.Bob Levine discusses why some fonts can’t be used on both Mac and Windows, and how to get around this problem in some instances.
Q: I’m working on a document with a colleague. We’re sharing all resources in a Dropbox folder. My colleague has shared a packaged folder with me including a “Document fonts” folder. When I open the InDesign file, I get multiple missing font messages. I’ve checked the fonts in the shared folder in Windows Explorer and some of them have a 0 kb size. My colleague is using a Mac and says they’re fine. Is this the problem? Is there anything else we should be aware of?
. . . .
This article is for members only. To continue reading, please sign in, or sign up for a membership today. Thanks for supporting CreativePro! CreativePro membership keeps you up-to-date with the technology, solutions, and resources to strengthen your professional development.
BECOME A MEMBER
For just $6.50/month (billed annually), you’ll get access to valuable benefits, including:
 |
We have that experience once in a while, but it’s not concerning Mac users and PC users. It seems if they zip their files (instead of using Mac’s compression or Stuffit, then the fonts get messed up when we open the file. I guess it’s because postscript font’s resource forks get wiped out? The suitcase fonts are okay, but the printer/postscript fonts show as 0KB and as simple text documents. If they use Stuffit, then they are fine.
We also had this problem if they kept their files on a PC server.
Thankfully, this rarely happens anymore for us. But several years ago it was a real issue.
As a note: I first noticed this back when OSX first came out. The resource forks would be lost it seemed, but the fonts were okay in OS9.
This is why Macs rule print publishing. Mac can use any font, Windows can’t.
IT guys always want to replace our Macs with PCs. I tell them this is not trivial. Our organization, and myself personally, own hundreds of thousands of dollars worth of Mac type 1 fonts going back decades – fonts that are sometimes not replaceable by Windows versions.
And our clients constantly supply working files with Mac type 1 fonts.
I tell IT the company owner will not pay for replacing fonts and will not accept us refusing to use the clients fonts, as they might pull their contracts.
Even if we do replace our publication template fonts (5 large magazines) and clients’ fonts, then they reflow and require massive editing, or risk errors.
If you’re creating a new publication, use OT fonts if you can, sure. But for large legacy libraries and for client supplied work, you may not have any choice. Some may say it “shouldn’t be that way” but it is the reality we work with.
As long as I use a Mac, I can use any the amazing fonts I have, no problem. If it’s not broken, don’t fix it.
If you use a Windows for print design, you’re far more limited (sorry). I have a Mac and a PC with Adobe CC, but the PC is only used for 3D rendering. Adobe CC is almost useless on windows because of the font limitations.
And don’t get me started on ripping Truetype fonts to .ps, .pdf and imagesetters :P
Why is my comment still awaiting moderation after two days?
And the site shows three comments, but none show up.
So, if I read correctly, there are workarounds for Mac users to use Windows fonts but Windows users just have to plan ahead and avoid Mac fonts? Just asking …
P.S. I mean, because sometimes the files come to me through my publisher client, and the publisher is the one who receives the files from the author, and the author may be on a Mac and request certain fonts to be used in their book and ….you get the picture. I’m in the middle and no way to warn an unknown author ahead of time, hey, don’t choose these fonts!