Hannes Hirzel wrote:
> Great, thank you for the quick answer! A thunderstorm this morning has
> just blown up our internet connection and I am writing this in a
> internet cafe. However I want to try this out ASAP.

You're welcome. I just posted another set of fixes for font rendering 
but there is one that I can't fix right now. Apparently, BitBlt got 
broken and no longer updates the text position after a primDisplayString 
call. This leads to problems if you use mixed font rendering. If you 
find that the spacing of certain characters seems to be completely wrong 
(like printed on top of each other) comment out the BitBlt 
primDisplayString primitive to see if that fixes it.

Cheers,
   - Andreas

> 
> Hannes
> 
> On 8/14/09, Andreas Raab <andreas.raab at gmx.de> wrote:
>> hannes.hirzel wrote:
>>> I use the updated Squeak3.10.2-trunk.image as of today.
>>>
>>>  603 asCharacter
>>>
>>> gives the result as shown in the screenshot. Any suggestions?
>> The issue was caused by a method which didn't use the proper two-pass
>> rendering for the new fonts. I've fixed this in the trunk (just update).
>>
>> However, our new fonts only cover Latin-1 range so using non-latin
>> characters with it won't work. In order to use non-latin characters you
>> will have to find a suitable font.
>>
>> You can do this by hitting Cmd-K (Alt-K) and go to the (equally new)
>> "More (non-portable) Fonts..." section at the end of the font menu. This
>> will offer you platform truetype fonts to use which hopefully have the
>> coverage you are looking for.
>>
>> Cheers,
>>    - Andreas
>>
>>
> 
>