What settings do you have under 'OpenType TT Encoding'?

André

Is there any special reason for generating Mac TrueTypes? »Normal« TrueType/OpenType TT should work just fine on Mac OS X.

@agisaak
Here they are:

@jens
Yes there is. The fine program of FinalCutExpress does not accept them properly. I had produced OT TTs but they wouldn't show up, allegedly its a known but unfixed bug.

Does anyone have any resource material for this type of stuff? I can't be the first one to wonder how the exact settings should be in FL for font production, am I?

Thanks
Henning

Try changing the first option to 'do not reencode first 256 characters'. (Just a stab in the dark).

André

The fine program of FinalCutExpress does not accept them properly. I had produced OT TTs but they wouldn't show up, allegedly its a known but unfixed bug.

Oh yes, video editing applications are among the last apps to handle fonts in a creative manner ;)

I remember we had a case where a video editing application applied kerning not based on what was specified in the kern table or what the letters actually looked like, but on what the letters usually should look like ;) Led to interesting results with custom icons in the place of unneeded glyphs ...

Change "Do not Export OpenType Names Record" to "Append OpenType name record to the names exported by default"

This is the setting I use, and never have any problems.

The fine program of FinalCutExpress does not accept them properly. I had produced OT TTs but they wouldn't show up, allegedly its a known but unfixed bug.

Do you, or anyone else, have some more details?

"Use following codepage for first 256 glyphs" must be set to "Do not reencode first 256 characters".

This option remaps the Unicode codepoints of the Windows 1252 codepage to something else (in you case, MacOS Roman), which results in a font that is not fully Unicode-compliant. Settings other than "Do not reencode" in this option are only for users who need to make custom-encoded TrueType fonts that should work with VERY old non-Unicode applications (such as, say, Adobe PageMaker 6.5 or Illustrator 7).

A.

Adam, doesn't this suggest that this option is better hidden if not removed in a future FLS version? Since making non-OT/TT fonts has almost become an exception, this "dangerous" option is presented in a too prominent way in FLS5, being number one on this FontInfo page. Same for the option that follows -- generating a Mac-specific cmap subtable may be unnecessary already. Perhaps put both into a box whose interface elements can be deactivated with a checkbox (which should be the default) ...

Thanks everyone so far for your comments. I will try your suggestions as soon as I get to my FLS tonight.

One last try: Does anyone know of a detailed desriptions (website, pdf) how to set the preferences in FLS for font prodution?

H.

Don't know of any, unfortunately. The FLS5 manual is pretty detailed and offers background information too. Settings in Font Info and Preferences for font export depend much on what kind of font you are about to make, hard to summarize in a simple how-to.

I guess that may be of little help, but I tried out various TTF fonts in Final Cut Express 4.01 on 10.6.6, and couldn't see any problems.

Karsten,

you are right, there are a few options that should be hidden/removed from the UI.

Best,
Adam

Jens, Adam, thanks!

@twardoch @jmontalbano
thanks for the advice - it works now very nicely!

thanks everyone for the input!

H

Karsten,

I know Final Cut had problem with non AAT TT fonts for Arabic script (TT Arabic fonts with OT flavour). I don't have Final Cut and I can't tell whether the problem persists or not.

-b