On 19.05.2010 21:44, Stéphane Ducasse wrote:
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
As you've noted, we've already done it.
It's broken then display of WideStrings with StrikeFonts, since that relied on Wide Characters being stops, which did happen when leadingChar was 255, but not when it's 0. That is manifested in that the rest of the string after a WideChar is rendered as ?'s. There's also an error causing the width of the chars to be wrong, and the first char on the line to be displayed on the previous line instead, but iirc that's not directly related to the stops issue.

Cheers,
Henry

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to