It’s a Windows font.
Try moving the files into the Fonts folder inside the InDesign folder.

.bmap is not a Windows file, it's a bitmap cache representation of the 'real' font. The AFM file is useless on its own, and so is the .lst file (that is not a part of a standard Type 1 Font distribution and can be anything).

You cannot use the .bmap font in InDesign because that needs real fonts, not just bitmaps. It might work in other programs, though -- I dunno, always avoided them like the proverbial plague.

I'm wondering about the untyped file -- OS X doesn't know what it is, so it presumes it's an 'executable', but you can be pretty sure it's not one. Can you open it with, say, Textedit, and see if it contains readable data, or just a jumble of strange characters?

If it starts with something akin' to

%PS-AdobeFont 3.0
%% All rights reserved bladibladibla
%% Some more stuff...

it's the one file type I'm missing from your list, and you can try again after adding the proper .PFB extension to it.

hi riccard0

thnx for replying, i tryed putting the fonts in the indesign folder but no luck?

anny other ideas?

It's possible that you have a Mac PostScript Type 1 font in which the resource fork has been unintentionally stripped out of the .bmap file. Mac screen font files often have that file extension. A Mac Type 1 font can't be used on a Mac if the screen font file is missing or corrupt.

If you "get info" on the .bmap file, what is the file size? If it's 0k (zero k), then the .bmap file has become corrupted. This can happen when emailing or ftp'ing Mac font files without first compressing them.

hi thnx for trying to help...i checked some stuff

the .bmap file have indeed zero file size, mmmm so i guess the fonts on the cd the designer gave us don't work. I'm going to contact him, so i should tell him to compress them first, is using zip ok?

is using zip ok?

The font has to be residing on a Mac in order to be any use to you, so have him Stuffit...

zip compression sometimes strips out Mac resource forks. It depends on the specific program/version; the zip utility included with MacOS X should do fine.

Stuffit compression (http://www.stuffit.com/) handles Mac resource forks more reliably.

Starting with Mac OS 10.3, the Finder includes compression, under the File menu as "Compress (whatever is selected)", or if you right click on a folder or file. This will create a .zip file. If you compress a Mac file with a resource fork (such as an old style Mac screen font file), it will be preserved when the file is decompressed on another Mac. No need for StuffIt unless you or the other party are using a version of the OS older than 10.3.

>...could someone [please] say what we are doing wrong here, pretty please!! :D

You are counting on a graphic designer to be your font vendor.

I convert pfb files in TypeTool and come up with an otf font. I think having a font conversion application is a must for a design studio.

Isn't the exec mean its a Windows compressed file that will not work on mac? Sounds like you need to get ahold of the company from whom you purchased it and explain that you need a Mac compatible version. I think if you already paid they would be happy to correct the situation.

That would be a .exe file. OS X, if it encounters a file with no extension and no creator/type metadata will sometimes display an icon that indicates it's a UNIX executable file. Looks like this:

That's what the original poster was describing.

I would ask also on the Mac forums. I had trouble installing a font until I tried dragging the font to the different folders that were in the folder area. Both obvious suggesions, I know.

If the screen font file is corrupted (which it appears to be in this case), it will be impossible to install, no matter what folder it's placed into.

Incidentally, the file with the ".lst" extension is added to font folders by certain Adobe apps (maybe just Acrobat). It is not part of the font. More like preference or cache file used by Adobe.