Well since we are working with macroman, unicode and latin-1 let me  
remind folks of an outstanding issue with VM File names/paths.

On the mac the vm is shipped with VM path names set to be macroman,  
and you can change that choice to latin-1 or utf-8.
People that changed the VM to latin-1, then discovered that there are  
characters like (option-f) ƒ which are valid
characters to put in folder names/file names that then will NOT  
convert from utf-8 to latin-1, the conversion fails and you're toast.

Ok, fine leave as macRoman, then add in that you are taking the  
macroman path name and pretending it's latin-1, this means of course  
what you see in the file browser isn't reality.
Fortunately the character code isn't tampered with it's just  
displayed wrong, so using the path does the right thing.

Likely one might consider using utf-8, and then ensuring display  
usages of pathnames do the right thing....


On 13-Jun-06, at 10:09 AM, Bert Freudenberg wrote:

> I just hacked a bit of Unicode support into the truetype fonts. See  
> attachment.
>
> - Bert -
>
======================================================================== 
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
======================================================================== 
===