I've been PC based for 9 years now. This is the first time I've had a major conversion issue. I bought Crossfont, and that fixed it. (Not 100%; I still had to make some adjustments within the doc -- should have just bought the font!)
Jane, the Menu Maker
BTW -- Always looking for good freelancers!
To the best of my knowledge, Mac and Win PostScript and TrueType fonts are different and not cross platform compatible. OpenType fonts are truely cross platform. I hear that you can use Win TT fonts on a Mac, but not vice versa.
As I understand it, print service providers are reuired by the font EULA to own the font even though the customer provides it.
I suggest you ask your customer to purchase the modern OpenType versions of the fonts.
my mac friend cannot open my Word documents (with/without pictures) via email. How do I resolve so he can open themj?? Thanks!
Thats not an Adobe question. Perhaps it's because of the way you are sending the emails tho.
Send as plain text or have him download http://www.joshjacob.com/macdev/tnef/index.html
Here is the breakdown:
Windows can use OpenType, Windows Type1 and Windows TrueType fonts.
Windows cannot directly read Mac TrueType or Mac Type1 fonts.
Macintosh can use OpenType, Mac Type1, Mac TrueType, and Win TrueType.
Adobe products can read some Windows Type 1 fonts if installed in the correct folder.
I recommend TransType Pro from FontLab.com for converting fonts to OpenType (keeping in mind any legal issues from the font foundry). Better yet, switch to OpenType Pro fonts from Adobe.
We invested in TransTypePro, it was a cheap investment considering the time loss of running round trying to find the right version of the fonts.
Its 2015 now why doesn't any huge company like you guys create a format that carries both the PC and Mac font so this problem wont happen any longer. But then I blame Windows mostly because I'm budgeting for a Mac due to one of these problems. But then here is an idea for you, why don't Adobe create more space in Adobe files that carries the original fonts for both the PC and/or Mac font so if you receiving a file you wont have to download it first.
Agree - what an ancient problem that requires real attention.
The fact is that the industry solved this problem over 15 years ago. Microsoft, Apple, and Adobe along with other industry participants developed the OpenType font format which is fully cross-platform compatible. It supports both TrueType-like and Type 1-like fonts within a wrapper that supports advanced typographical features, multiple character sets, and a very large number of glyphs all in a single font. No more so-called “expert sets,” no more separate metrics files, no more separate “screen fonts,” etc. And font is fully cross-platform compatible (i.e., you can literally copy them back and forth between Windows and MacOS-based computers without loss at all. The fonts totally use what to MacOS users see as a file's “data fork” instead of the MacOS-only (i.e., not available on Windows or any flavor of UNIX) file “resource fork.”
We have been trying to warn our customers that this is the solution going forward for quite a few years now, especially since (1) many projects require collaboration between users using mixtures of Windows and MacOS systems and (2) recent versions of MacOS don't even support the MacOS flavor of Type 1 fonts anymore (and Microsoft's own Office applications don't support Type 1 fonts at all under Windows - although they do support OpenType fonts with Type 1 outlines, i.e. OpenType CFF fonts).
The most reliable way to transition from platform-specific Type 1 fonts or MacOS TrueType fonts (they also don't work on Windows systems due to both differences in file format and their residing in a file's resource fork which is not supported under Windows or Unix) is to license OpenType versions of the fonts you have been using, preferably from the vendor who licensed the Type 1 version of the font to you many eons ago. Alternatively, you may need to use special software that can convert fonts from those legacy formats to OpenType (note that such conversions can be “lossy” in terms of font metrics and design, especially if you don't carefully use such tools). The first solution, licensing new OpenType versions of your older fonts has a higher initial cost in terms of reassigning fonts to styles, dealing with special character sets, and assuring no significant relayout issues, but in the long term, it is an investment well worth it in terms of flexibility and avoiding some time where those older fonts may simply not be supported at all for new documents.