I don’t know about doing your idea, but you can pre-compose a list of preview strings and then save as a plain text file. This can be imported into the Metrics window by clicking on the “...” button in the lower right corner and then the folder button in the upper right of the Load Text window.

Once you import your list of preview strings, you can cycle through them quickly using the up and down arrow keys on your keyboard. You can also select a specific preview string from the pop-up menu to the left of the “...” button in the lower right corner of the Metrics window.

It can take a while to pre-compose your list of preview strings, but once you do it you can use them as often as you like. It’s a time saver in the long run.

yes, I think I’ll create a textfile, but it will be rather big: Glyph-names like “eight.denominator” aren’t very handy as well...

…but once you have your list, you can always use it again for the next fonts. A lot of time and energy the first time, but it will pay dividends later ;-)

I think I’ll create a textfile, but it will be rather big

You may need to break up into smaller files if it gets too big. I’m not sure exactly what the limit is, but it seems to be 32k, at least on the Mac version.

BTW, Sebastian, it’s definitely a very bad idea to name your small caps glyphs “Asmall”. Use “A.smcp” or “A.sc” or “A.small” instead.

A.

Adam,

I had been wondering about that — It wasn’t too long ago when “A.smcp”; “one.op” etc. was the recommendation. But now all Adobe’s fonts seem to come small caps named “Asmall” etc., and a Unicode index assigned from the private use area.

Eliminate Private Use Encoding in Revised Fonts?

I thought Adobe was moving away from using PUA.

What I would do is make a new text file with just the “HHOHHADAHHOHH” strings, run a find and replace to replace “H” with “/Hsmall”, “O” with “/Osmall”, etc. and paste this into your original text file with “HHOHHADAHHOHH” and “nnonnadannonn” etc.

- Lex

> But now all Adobe’s fonts seem to come small
> caps named “Asmall” etc., and a Unicode index
> assigned from the private use area.

Are you talking about ancient Adobe fonts (1999-2001) such as Adobe Garamond Pro, Adobe Caslon Pro, or recent Adobe fonts (2005-2006) such as Brioso Pro, Garamond Premier Pro? If you’re looking at the ancient fonts, please no longer do so.

A.

>Are you talking about ancient Adobe fonts (1999-2001) such as Adobe Garamond Pro, Adobe Caslon Pro, or recent Adobe fonts (2005-2006) such as Brioso Pro, Garamond Premier Pro? If you’re looking at the ancient fonts, please no longer do so.>

Well, somewhat new — like Chronos Pro Light (creation date 2002) still uses “Tsmall” and “oneoldstyle.” But whatever. I do notice that Garamond Premier Pro does assign a PUA number to all the small caps & oldstyle figures. (And I can’t resist — if 2001 is “ancient,” I must be “decomposed.”)

Charles,

OpenType was introduced in 1999. Today, we have 2006, which is seven years later. The Christian civilization is 2000 years old. In these terms, OpenType fonts made in 2000 are located in the 280s, which was when the Chinese were the first to use the magnetic compass, and emperor Aurelian invaded Gallia and was trying to conquest Persia. Fonts made in 2002 correspond the 850s when the Vikings invaded London and Constantinople, and Cyril and Methodius were on their way to the Kazakh lands.

It is somewhat new times, but well, not really so new.

Adobe recently announced that their next OpenType fonts will no longer use PUA.

Regards,
Adam