On Mar 17, 2006, at 4:41 PM, Yoshiki Ohshima wrote:
>
>   I think I asked this once before, and I apologize if I have missed
> the response from you, but can you tell me a bit about the
> modification you made?

My modification is very simple - hard part is finding/importing good  
quality korean font - I only did create UnicodeEnvironment (subclass  
of LanguageEnvironment) because all other subclasses of  
LanguageEnvironment uses different charset from Unicode. And I  
configured squeak to use UnicodeEnvironment instead of default  
Latin1Environment.

>
>   Using exclusively UTF-8 (for the external encoding) will be too
> limiting in many applications on many platforms.  It is a good idea to
> use a single internal representation, and Unicode is a compromization
> today for this purpose (and Squeak uses it, too.)  But there is no
> good reason to limit the external encoding.

I totally agree on this.

PS)
I've encountered new problem. If file name is UTF-8 encoded Korean, I  
can only see ????.txt instead of 한글.txt in squeak. (FileDirectory  
class) I think this is related to VM part but not sure.

Hope this can help you.