Hi,

Jocel wrote:
> I've posted my comments about localization problems before (sadly, the 
> Yahoo archive doesn't go back that far. Here is a reference that loads 
> 1MB - http://www.create.ucsb.edu/squeak/9710.html#Letter406). I was 
> more worried about translating the programming language itself rather 
> than just strings, but my solution would handle both.

  I remember your article.

  If the example is something like:

------------
'<person> have <number> <animal>'
     printWith: {#person. {'I'. 'You'. 'She'} atRandom.
                 #number. {one. two} atRandom.
                 #animal. {'dog'. 'fox'} atRandom}
------------

even English is hard to handle and languages like Portguese
and German, that have the genders, the situation would be
worse.

  I believe that the good ability of
reading/writing/speaking the mother language is more helpful
for kids to acquire more things in long-run.  If I would
have kids, I hope they would learn *correct* mother language
before learning programming.  I wouldn't want to teach them
some compromized (wrong) sentenses.

  I'm sorry I can't suggest any good ideas, but natural
language issue is certainly time-consuming.  I'd say I want
SqC to put higher priority on "cutting edge" or "break
through" type of works.

-- Yoshiki