ok
may be you should have said that before :)
Now how this can be done?
changing the EncodedCharSets?
> initialize
>
> self allSubclassesDo: [:each | each initialize].
>
> EncodedCharSets := Array new: 256.
>
> EncodedCharSets at: 0+1 put: Unicode "Latin1Environment".
> EncodedCharSets at: 1+1 put: JISX0208.
> EncodedCharSets at: 2+1 put: GB2312.
> EncodedCharSets at: 3+1 put: KSX1001.
> EncodedCharSets at: 4+1 put: JISX0208.
Then I do not understand because
EncodedCharSets at: 0+1 put: Unicode
seems to me that this is already the case but may be I'm not looking at the
right place.
What are the implications?
What will we break.
Stef
On May 19, 2010, at 9:06 PM, Philippe Marschall wrote:
> On 19.05.2010 19:35, Stéphane Ducasse wrote:
>>>>
>>>>
>>>
>>> Currently the semantics in Pharo are
>>> 0: Latin 1
>>> 255: Unicode
>>>
>>> which is fun because the first 255 characters are interned and you
>>> therefore can't change their leadingChar. So if you're using Unicode,
>>> you're forced to mix leachingChars.
>>
>> so what do you suggest to have unicode as zero?
>
> Yes, the decision of Squeak 4.1 to make Unicode leadingChar 0 is an
> improvement.
>
> Cheers
> Philippe
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
