Seems a good idea to bring up an issue which also needs addressing.

Right now the primitives that supply or take file names/paths expect to  
see MacRoman characters
which then map mostly to the apple fonts for display, or better to the  
AccuFonts which actually gets things right.
However this isn't helpful for folks which can insert unicode  
characters into file names.

Now what I'm proposing is to change the mac os-x vm  return and deal  
with UTF-8 strings.  That way
picking a unicode based file will later allow the opening of the file.

I welcome comment.


--
======================================================================== 
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
======================================================================== 
===