We've been through all this before, but it's worth making the
distinctions one more time.

There are four different things:

(1) Which KEY you press for the assignment symbol (or the return symbol);
(2) which GLYPH is rendered on the screen;
(3) which CHARACTER(s) Squeak programs see in a string;
(4) what ENCODING is used in a file.

There is also a rather nasty font bug:
some of the "Squeak fonts" display DIFFERENT glyphs at different sizes.
If anything is calculated to make Squeak look amateurish, that is.
For this reason, the old Squeak fonts must go; I hope that 3.7 will
use the new free fonts out-of-the-box.

The fact that there isn't any left arrow or up arrow key on my keyboard
really isn't relevant.  (Actually, my keyboard has 3 keys labelled left
arrow and 4 labelled up arrow.)  My keyboard doesn't have any key
labelled "e" either, but that doesn't stop me typing "e".  Nor does it
have any key labelled with any accented letter, but that doesn't stop me
typing the full range of ISO 8859-1 printing characters.

The important issues appear to be the external encoding.  We've talked for
a long time about switching to Unicode/UTF-8.  The book "Learning Cocoa"
says "Cocoa uses Unicode ... as its native character set"; Windows also
does this; Unix systems like Linux and Solaris support Unicode to a greater
or lesser degree also.  If you want to deal with HTML 4, let alone XHTML or
XML in general, Unicode it is.  (Of course, unlike dear old Unicode 2 with
its 16-bit character set, Unicode 4 really requires 21 bits per character.)
Supporting Unicode isn't going to be easy, not at all.  But won't we look
the great idiots if we go back to the dead days of ASCII-only (abandoning
left arrow for colon equals) at a time when the rest of the world has
access to a large character set including a full range of arrows?

The internationalisation steps being taken for 3.7 are HOORAY! GREAT STUFF!
wonderful, but they are only the beginning.