Stefan,

I'm uncertain how it came to pass that some font names include the 
size and others don't, but an update in the pipeline now (1790) 
cleans things up so that it doesn't matter: font names will now 
appear uniform to the user (in all the various font menus) and the 
pointSize rather than the font "height" will be shown, and you will 
no longer see two numbers per font in menus.

Thus, when importing fonts, you can use either convention (i.e. 
either include the pointSize in the name or not) -- it will look the 
same to the user either way.

   -- Scott

At 1:33 PM +0100 12/28/99, Stefan Matthias Aust wrote:
>I think, there's an inconsistency with font names.  Shall they contain the
>pointSize in its name or not?  NewYork has while ComicPlain has not.  It's
>good to be able to distinguish different strike fonts of one family but
>this leads to strange looking popups as they offer "Bookworm20 35" now
>instead of "Bookworm 35" (acutally, I'd prefer to see the pointSize,
>"Bookworm 20", not the pixelSize here).
>
>So the bug is either the added or missing pointSize or the way, the text
>style popups are created.  I created a bunch of fonts and I'd like to name
>them the right way, so please advice.  I'll then volunteer to do the needed
>changes.
>
>BTW, I'd suggest to make #readFromStrike2: a class method and to remove
>that "halt" statement.
>
>bye
>--
>Stefan Matthias Aust  //  Bevor wir fallen, fallen wir lieber auf.