Oh well, I guess Bob is right. There isn't actually any such thing as a
#characterNotInFont anymore. Every character has a glyph (which might be the
"character not in font" glyph) but there's no reason why a character should
not exist in the font.

Now should I feel sorry or not for "accidentally fixing" this?!

;-)
  - Andreas

> -----Original Message-----
> From: Bob Arning [mailto:arning at charm.net]
> Sent: Thursday, June 01, 2000 2:06 PM
> To: squeak at cs.uiuc.edu
> Cc: recipient list not shown
> Subject: Re: [BUG] Celeste - names with non-ascii characters
> 
> 
> On Thu, 01 Jun 2000 12:57:04 +0200 Stefan Matthias Aust 
> <sma at 3plus4.de> wrote:
> >At 20:17 30.05.00 +0300, you wrote:
> >>When showing a message from "Göran" Hultgren <gohu at rocketmail.com>,
> >>Celeste cuts off the line in the TOC right after the $G.
> >>
> >>Anyone have any idea why?
> >
> >How does one reproduce this bug.  If I try
> >
> >'Göran' displayAt: 0 at 0
> >
> >it works.  If I compose an email with that name, it also 
> works.  If I 
> >create a StringMorph and edit its contents to include 
> äöüßÄÜÖ, it works, too.
> >
> >I'm using the latest 2.8a.
> 
> Stefan,
> 
> This one looks to have been fixed by Andreas' 
> font/character/scanner repairs in changesets 2179 through 
> 2182. Prior to that,
> 
> StringMorph new contents: 'Göran'; openInWorld
> 
> would show as just a 'G'.
> 
> Cheers,
> Bob
>