Issue 6183 in pharo: Unicode initialization is the inverse as it should be

Status: Accepted
Owner: [hidden email]
Labels: Type-Seed Milestone-2.0

New issue 6183 by [hidden email]: Unicode initialization is the  
inverse as it should be
http://code.google.com/p/pharo/issues/detail?id=6183

it should first initialize the unicode data and afterwards the case mappings


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

Updates:
        Status: FixToInclude

Comment #1 on issue 6183 by [hidden email]: Unicode  
initialization is the inverse as it should be
http://code.google.com/p/pharo/issues/detail?id=6183

Name:  
SLICE-Issue-6183-Unicode-initialization-is-the-inverse-as-it-should-be-GuillermoPolito.1
Author: GuillermoPolito
Time: 27 June 2012, 12:37:45.636 pm
UUID: a4f97e11-4ea0-483f-a4e5-720dfdea6299
Ancestors:
Dependencies: Multilingual-UnicodeInitialization-GuillermoPolito.3

fixed unicode initialization order


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

Updates:
        Status: Integrated

Comment #2 on issue 6183 by [hidden email]: Unicode initialization  
is the inverse as it should be
http://code.google.com/p/pharo/issues/detail?id=6183

in 2.0 164


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