Am 08.05.2012 um 15:37 schrieb Henrik Sperre Johansen: > TLDR of non-bug related stuff; If it were up to me, I'd say nuke leadingChar > from orbit (which, as you say, is already done in most cases), > then find some other way than what is currently done in LanguageEnvironment > (if possible) to query the correct encoding of strings you pass to the system.
+ any number you can imagine It is easy to state that it is broken now and leadingChar causes harm. So nuking it will probably just inverse the problem situation but then it can be cured somehow by fixing the bugs. Handling the characters right in encoding is only one side of the medal. Characters and strings are still need to be comparable. To get this right it would mean to have support ICU [1] in pharo which is a good idea anyway. Well, if it is doable in a pluggable fashion of course. Norbert [1] http://site.icu-project.org/
