|
| windows xp pro and postscript fonts |
 |
Tue, 26 Jun 2007 11:04:39 -070 |
I've migrated over from an old mac to a new xp pro x64 machine. When I go into
fonts_add new fonts windows does not see the postscript font, only tt. Any ideas
as to what to do next?
Thank you
|
| Post Reply
|
| Re: windows xp pro and postscript fonts |
 |
Tue, 26 Jun 2007 12:10:44 -070 |
By PostScript fonts, I will assume you mean Type 1 fonts. Since TrueType fonts
are supported directly by PostScript and PDF, they are also PostScript fonts.
I also assume that you know that Type 1 fonts are in a different file format for
Windows than for Macintosh. As such, you cannot install your Macintosh Type 1
fonts under Windows. Windows Type 1 fonts each require two files for
installation, a .PFB file (containing the font outline, hinting data, and basic
font metrics) and a .PFM file (containing extended font metrics including
kerning data). If you point the Windows Font Control Panel to a directory
containing both a font's .PFB and .PFM files, you should have no problem
installing Type 1 fonts under Windows 2000, XP, or Vista. There is no need for
ATM or any other software to install such fonts (with the exception of Multiple
Master fonts).
|
| Post Reply
|
| Re: windows xp pro and postscript fonts |
 |
Tue, 26 Jun 2007 13:58:51 -070 |
To add to what Dov has said ..
It is technically possible to convert Type 1 fonts from Mac format to
PC format, but such conversion MAY violate the terms of usage or
license agreement for the particular font. You can find the terms for
most major foundries on their website or they may have been delivered
with the font.
Some will completely restrict such conversions, others may or may not
include it the the number of systems a font can be installed on.
Almost any rational or irrational combination of terms may appear!
You'd have to investigate each one.
Some Mac font families are named in such a way as to become almost
unusable under Windows with anything other than Adobe applications.
Windows only recognizes normal, bold, italic, and bold-italic as
"styles". Many Mac font families will use "styles" to
differentiate
fonts variously described as light, outline, smallcaps, etc. Windows
and Microsoft applications will give unpredictable results. For
instance, it may decide to give you the same font whether you ask for
the regular or smallcaps version.
That said, there are programs such as CrossFont (ASY) and TransType
(Fontlab) that will do loss-less conversions, but you may have to
manually monitor the conversion to make sure that the internal
font-names are usable.
|
| Post Reply
|
| Re: windows xp pro and postscript fonts |
 |
Tue, 26 Jun 2007 15:11:40 -070 |
Further note that in addition to the concerns Herb notes, not all the metrics in
the Mac's Type 1 font (actually stored in the so-called screen fonts) correspond
exactly to all the information stored in the Windows .PFM file and vice-versa.
In addition to any legal issues, be careful what hacking around you do with
fonts. Your time is worth more than you think. Lost time due messed up jobs and
"redos" due to subtle incompatibilities are much more expensive than
licensing the official version of the font for the "other platform."
|
| Post Reply
|
| Re: windows xp pro and postscript fonts |
 |
Tue, 26 Jun 2007 16:33:36 -070 |
Dov Isaacs wrote:
"... not all the metrics in the Mac's Type 1 font (actually stored in
the so-called screen fonts) correspond exactly to all the information
stored in the Windows .PFM file and vice-versa..."
Thank you for that piece of information. I never knew that, and had
always thought that unlike format conversions, cross-platform
conversions were lossless.
- Herb
|
| Post Reply
|
|
|
|
|
|
|
|
|
|