Thanks Yoshiki

It seems so easy when you say it :)
I'm learning the hard way encodings :)
I want to go over the OLPC changes (but I have to understand a bit  
more than the basis)
But I'm learning something new so this is cool.

So first question:
	can I freely put
	EncodedCharSers at: 0+1 put: Unicode?

What the order in EncodedCharSets represents? Is it the way the  
encoding by default are looked up?

Thanks master

LukeStef trying to fly with his saber lazer

On Sep 24, 2008, at 7:31 AM, Yoshiki Ohshima wrote:

>> An easy workaround is to allocate Unicode in place of nil in:
>> EncodedCharSet class>>initialize
>> "
>> 	self initialize
>> "
>> 	self allSubclassesDo: [:each | each initialize].
>>
>> 	EncodedCharSets _ Array new: 256 withAll: Unicode.
>> 	snip...
>>
>> A better feature would be to prevent recursive Debugger  
>> invocations...
>> But that is a little harder I guess.
>
>  And for a system like Pharo that really doesn't have to carry the
> big burden from the previous version, Unicode can be the first entry,
> and the other language environments can be reordered to pack the
> entries in EncodedCharSets.  (Along with the all name changes and
> cleanup.)
>
> -- Yoshiki
>
>