The dialog has a list of possible encoding options when a Type 1 font is generated:
When you generate a Type 1 font, the most important encoding choice is to choose between one of two encoding forms:
Standard Encoding custom encoding
Standard Encoding is a special Type 1 encoding created by Adobe
Systems. Instead of enumerating all the code positions in the font, the Standard Encoding font leaves the actual encoding to the system font driver, and on the other hand, the system font driver knows what characters can be expected in the font. StandardEncoding is the
recommended choice if your font is a typical Western Roman font. If you generate a Mac Type 1 font (on FontLab Studio for Mac) with Standard Encoding, Mac OS will “know” that the font is a standard Western Roman font and will automatically match the font’s encoding to the system Mac Roman codepage. Similarly, when you generate a Windows Type 1 font with Standard Encoding, Windows will know that the font is a standard Western Roman font and will automatically match the font’s encoding to the system Windows 1252 Western (ANSI) codepage. Also, if the user of such fonts create documents in some applications (e.g. QuarkXPress for Mac and Windows), the applications will automatically re-encode the documents when moving between platforms.
Custom encoding is any Type 1 encoding that is explicitly specified in
the font. If the primary character set of your Type 1 is not Western Roman but Central European, Cyrillic, Greek, or Arabic, you need to select the appropriate encoding in the Names mode encoding selector in Font Window, and generate the font with custom encoding.
How Windows ATM Interprets a StandardEncoding
When a Type 1 font has StandardEncoding ATM assumes that this font includes all the glyphs from the first 128-glyph range (digits, alphabet and basic punctuation) and the European glyphs (128-255 range). The first 128 glyphs are called the “top zone”. The 128-255 range is called the “bottom zone”. The Adobe StandardEncoding includes very few glyphs from the bottom zone compared to the number of glyphs in the WinANSI (actual Windows encoding) encoding. When a Type 1 font in StandardEncoding is installed with ATM, ATM uses a special encoding instead of the “real” StandardEncoding as it is documented in the Type 1 format specification. This special Windows encoding is called the Default Encoding in FontLab. So if you create a StandardEncoding font and want to see how it will work in Windows, select the Default Encoding in FontLab.
Here is an explanation of the possible encoding export options: Select encoding
automatically This is the recommended setting. Generates the font with Standard Encoding if the Font Window is in Names mode and the encoding selector shows one of the following: “Adobe Standard Encoding”, “Default Encoding”, “MS Windows 1252 Western (ANSI)” or “Mac OS Roman”. Otherwise, a custom encoding will be generated
Always write
custom encoding FontLab Studio will always generate a custom encoding – even for Western Roman fonts – with the encoding currently selected in the Font window Names mode. Note: Western Roman Type 1 fonts generated with custom encoding may not work as expected
Always write
Standard Encoding Always generates the font with the Standard Encoding regardless of what is selected in the Font window Names mode
Export Unicode codepage if codepage mode is active
Exports a custom encoding based on the currently selected codepage if the Font window is in Codepages mode.
We recommend setting the Select encoding automatically option as the
default, because it covers most exporting situations very well.
Export only
encoded glyphs When enabled, all glyphs that are outside of the encoded “yellow area” will not be included in the generated font.
Tip: This can be used to quickly generate a series of Type 1
fonts from a large multilingual .vfb file that includes an extensive character set.
Automatically sort
glyphs This option allows FontLab to sort glyphs accordingly to the selected encoding on export. It is recommended to leave this option enabled.
If the Open Type 1 Export Terminal option is switched on and you
generate a Type 1 or Multiple Master font, the following dialog box appears:
As you can see, this dialog box previews and allows you to edit text data contained in the “open” and “private” sections of the exporting Type 1 font file. Use the Select a data section control to choose the part of the Type 1 font file that you want to edit and modify the text in the edit field below. Note that there is no external control of changes you make in the export terminal. Use it only if you really know what you are doing or you may create a font which will not only be unusable, but can even crash your operating system.
Refer to the Type 1 font format specification
http://partners.adobe.com/asn/developer/pdfs/tn/T1_SPEC.PDF
Use WinAscent and WinDescent as font vertical size
When disabled, the Type 1 font will be generated with the vertical metrics information based on Font Info > Metrics and Dimensions > Key dimensions > Ascender / Descender.
When enabled, the Type 1 font will be generated with the vertical metrics information based on Font Info > Metrics and Dimensions > TrueType-specific metrics > WinAscent / WinDescent. This can be used to generate a Type 1 and a
TrueType / OpenType TT font that both have identical vertical metrics.
Note: We recommend disabling this option
Autohint unhinted
glyphs When enabled, all glyphs that include no hints will be autohinted
Export FSType (font embedding) parameter
When enabled, the embedding information (Font Info > Names and Copyright > Embedding) will be written in the
Type 1 font. Note that this is a custom extension to the Type 1 font format and is not supported by all devices so we
recommend keeping this option disabled.
Type 1 Autohinting
When this option is enabled and a glyph is autohinted, existing hints will be removed.
When disabled, the automatically generated hints will be added to the existing hints. Note that this may cause some unwanted interferences.
Generating OpenType & TrueType
These settings control some technical parameters of fonts that you generate in the TrueType / OpenType TT (.ttf) or OpenType PS (.otf) format:
Automatically
reorder glyphs If this option is enabled, FontLab Studio will try to reorder glyphs to match the Mac cmap encoding table. Technically, this is a requirement of the Apple TrueType specification but it is not required on Mac OS X or Windows.