Your "Also" suggests that your Opentype features indeed do not work. Although it's a mystery why your font does compile without errors as OTF TT file but not as OTF Type 1. (Which begs the question, by the way, why you are doing that?)

Why am I compiling as a TTF? I did that to try out different file formats – to see which ones would work.

Dump all of your OpenType code. Then add features and test compile them one at a time until you find the broken one.

test compile them one at a time until you find the broken one

Assuming it is only one gefuched feature -- always risky -- there is a faster way than one at a time. Dump half of them. If that complies, try the other half. Keep splitting in halves. You'll find the bad one a lot quicker this way.

Thanks for the feedback – I really appreciate everyone taking the time to out here. I'm new to this, but if I understand correctly, the OpenType code should be accessible in Window > Panels > OpenType. When I open that up, there is no code or classes listed – it is completely blank. Is this the problem? Do the small capitals and old style numerals need to be defined here in order to generate the OpenType PS file?

Keep splitting in halves.

Smooth. You're a closet CompSci guy aren't you?
http://en.wikipedia.org/wiki/Binary_search_tree

hhp

the OpenType code should be accessible in Window > Panels > OpenType. When I open that up, there is no code or classes listed – it is completely blank. Is this the problem?

Yes

Do the small capitals and old style numerals need to be defined here in order to generate the OpenType PS file?

Yes. Well, not necessarily "defined." You need (1) a set of classes and (2) a set of instructions as to what to do with the classes. You can put both in the features file, or you can use the classes file to "define" them. I prefer to have everything in the features file. In fact, I prefer to have that file written off so as to be able to use a text editor on it.

You might have to read the manual...

Thanks charles_e. Been going through the manual – it's been hard finding where to start with that though. This helps a great deal though. It looks like they start dealing with this topic on page 833. My plan is to use the manual and some other font's code as reference to move forward with this. Thanks so much.

>Keep splitting in halves.

Super-nice! :^)

If it cuts in halves.What are the net effect of it?

painting contractors in west palm beach

Charles: ‘[…] there is a faster way […]’

Another option would be to collect all your OT layout features in one file, to download OTM Light 2.0 (which supports the AFDKO 2.5), and subsequently to use the File –> Import function to compile the features. In File –> Messages a detailed report of the compiling process will be listed. Compiling will abort in case of an error, of course, and there will be an indication presented of what went wrong.

Please note that the export of OT layout features in OTM Light 2.0 is not as perfect as in the latest OTM 2.4 full version.

FEB

Thanks for this. I've downloaded it and am figuring it out. Seems to be a bit ahead of where I am in the process, but I can see it being useful down the road. Right now, I'm still troubleshooting and learning how to correctly code the OpenType features.

Going through the manual. Wanted to note a couple of things here. I deleted all the OpenType code and it still would not generate an OpenType PS font. I added a small capital and old style numeral class, definition, and feature and it gives me this in the Output panel when I try to generate the font: "[WARNING] Glyph class @Fontname-Demi redefined [/Users/lukeatkinson/Library/Application Support/FontLab/Studio 5/Features/fontlab.fea 90]." Going to keep going through the manual. Not sure what FontLab is saying though.