InDesign lists font according to encoding, the idea being that all your Cyrillic fonts will list together, all your Greek fonts, etc. Fonts that do not have a standard encoding recognised by the application are listed at the bottom of the list.

> thnx, John. i'll hafta go back and study up on encodings for FontLab. So I'm asuming that Word doesn't follow a similar listing by encoding scheme

I'm interested to know what criteria FL uses for including
the encodings when using the auto function. I've developed
an extended latin charcter set covering CE languages. When I hit
auto in the Supported Codepages I get a few strange ones.
For instance, 857 IBM Turkish and 1258 Vietnamese.

Curiosly, fonts like Myriad Pro do not show up in this lower
portion of the menu while mine does. (They have nearly the
same glyphs, minus the Cyrillic)

What supported codepages relegate the fonts to the lower menu?

When I hit auto in the Supported Codepages I get a few strange ones. For instance, 857 IBM Turkish and 1258 Vietnamese.

Yes, it doesn't work Don't trust the auto codepage selection: it almost always adds Vietnamese and other non-supported pages. Codepage support is meant to be very specific: you are not supposed to claim support for a codepage unless you support all of the characters it includes. So the best idea is to manually select codepages that you know your font supports.

The InDesign menu has changed recently, I believe. I have not taken a close look at what InDesign CS does.

This was my hunch, but it's nice to be sure. Especially in
regards to the need to inlcude all characters for a defined codepage. I didn't know this.

As for InDesign CS, the fonts with multi script support still
rest at the bottom of the menu.