Adding Accufonts to the update stream (was Re: LicencesQuestion : Squeak-L Art 6.)

Edmund Ronald eronald at
Mon Feb 24 14:39:45 UTC 2003

Wouldn't about now be a nicee time to have full native Unicode support in
Squeak? I looked at the Nihongo Squeak port at one time for some
lexicography work, but the character processing routines were fearfully
slow, and the author told me this was an unavoidable side-effect of their
being written in Squeak rather than at some lower level ...

Of course, I am still a newbie, but having native Unicode might make
text-processing, searching, language parsing and web serving a more easy
proposition for people in multi-byte character environments. Assuming, of
course that president Bush allows people in other countries to stay alive
long enough for another version of Squeak to come out :(


On Mon, 24 Feb 2003, Ian Piumarta wrote:

> On 24 Feb 2003, Cees de Groot wrote:
> > I'm also assuming that MacOS X moves/has moved to ISO 8859, which
> > makes the MacRoman encoding even more an anachronism ;-)
> ...
> > Err, dare I bring the issue of Unicode, UTF-8, ... to the table?
> MacOSX uses Unicode internally and converts to UTF-8 for things like the
> filesystem which are limited to 8-bit chars.  I can't speak for the
> Carbonized Mac VM or CocoaSqueak, but the Quartz support in the 3.5 Unix
> VM handles MacOSX Unicode correctly and properly converts whatever
> keyboard layout and charset is selected in the prefs panel into MacRoman.
> (Changing it to convert to ISO-8859-N would require simply replacing one
> constant [kCFStringEncodingMacRoman with kCFStringEncodingISOLatinN] in
> the source.  Ditto for kCFStringEncodingUTF8.)
> Ian

More information about the Squeak-dev mailing list