It is a Windows-only font. If it were .ttf it would be usable but as it is, no.

I understand that it IS possible to use these in Adobe applications. For instance, to use the font in InDesign, install the two files in the Fonts-Folder in the InDesign-folder. DISCLAIMER. I do not have a Mac OS and have read this elsewhere.

However, it would be better to obtain the font in either OTF or TTF format.

For instance, to use the font in InDesign, install the two files in the Fonts-Folder in the InDesign-folder. DISCLAIMER. I do not have a Mac OS and have read this elsewhere.

I can confirm that this is correct for 10.8.1 and InDesign CS6.

It does work in CS 5.5 as well, however kerning does not seem to work though...

edit: this is not correct, it does seem to work. Very interesting, I did not know this!

That's good to know about; I'll have to give it a try, although I wonder how well the Windows encoding in the .pfb fonts will integrate. I think that might cause problems if the file went to someone else.

>>I think that might cause problems if the file went to someone else.

>>I have been given a Postscript type 1 outline font …

It might seem fonts travel a lot these days. Even the old ones. ;-)
Is that a freeware font or a custom corporate font or why was it just “given to you”?

As already mentioned, Type1 fonts are not platform-compatible. You can't install a Mac Type1 on Windows and you cannot install a Win Type1 on the Mac. They can be converted to .otf of the license permits it.

Note that in some jurisdictions EULA restrictions on such conversions are invalid (at least when they're done "internally").

BTW, I echo Ralf's concern with the "given" bit...

hhp

@Ralf

I always thought that windows Type1 fonts could not be used on Mac and vice versa, but why then do windows type1 fonts work in Adobe applications on Mac? I can not quite comprehend how this works...

why then do windows type1 fonts work in Adobe applications on Mac?

Mac OS (X) can’t understand it, but Adobe of course knows its own font format and just continues to support it internally. If the fonts are placed in certain font folders, apps like InDesign will check those folders and then just make those fonts available as if they were installed. After all, Type1 was a rather simple font format. ;-)
Note this works only for PC Type1 on the Mac. I can't work the other way around, because of the way the Mac Type1 fonts were stored in the resource fork of the file.

Was this possible before Apple changed to Intel?

@Queneau. Yes. It has nothing to do with the processor. Note that even in the early days of Adobe Acrobat Reader, under operating systems like Windows 95 and 98, Multiple Master Type 1 fonts were included in the package (used primarily for rendering) and you DID NOT NEED Adobe Type Manager ATM).

Interesting.
Let's say you install a type 1 font in the indesign fonts folder.
What would happen if you were to make an indesign document with that particular font, package it and send it to the printer?

The printer would then have
- an Indesign document
- a 'Links' folder
- a 'Document fonts' folder
That 'Document fonts' folder would then contain the same type 1 fonts as you put in your indesign fonts folder.

Would the printer then have to dig out those fonts, find the right fonts folder within indesign and put them there in order to make things work on his mac system?

Would the printer then have to dig out those fonts, find the right fonts folder within indesign and put them there in order to make things work on his mac system?

All of which could be avoided by sending them a PDF with the font subset instead.

> Would the printer then have to dig out those fonts, find the right fonts folder within indesign and put them there in order to make things work on his mac system?

No. As long as they open the document in the right relative position (the document fonts folder is alongside it) then InDesign will use the fonts just fine.

T