Am 13.07.2011 um 11:08 schrieb Sven Van Caekenberghe: > Any comments, Philippe ? > > Anyway, IMHO Unicode and UTF-8 are not broken in Pharo. It is perfectly > possible, as you know, to write Seaside web apps or pure web services that > deal correctly with Unicode through UTF-8, storing data is databases and/or > files, or sending it further along to other services. > > On the other hand, I can imagine that not everything that one could wish for > is already there, so slowly filling these functionality holes is important as > well. But unless we know what they are, we can't begin to make progress. > I like to second this. I can see the tension to not decode on image entrance and to not encode on image exit. This way strings are treated "to be just in transit" which is true for a lot of strings if you do a web service that pulls data from a database. But this only works if you assume everything is assuming the same encoding. While it has performance benefits I'm not fond of treating stuff like this. Encoding is just not to be ignored. To me the only way is to do it right everytime. I can't even believe the statement that there is less trouble by not do decoding. In average of the use cases the mess you create by e.g. by accidentially accessing magnitude information from those strings should be on par with the en/decoding troubles.
Norbert > > On 12 Jul 2011, at 22:45, Lukas Renggli wrote: > >> I don't remember. Ask Philippe, he is the expert on these kind of questions. >> >> Lukas >> >> >> On 12 July 2011 22:37, Sven Van Caekenberghe <[email protected]> wrote: >>> Lukas, >>> >>> On 12 Jul 2011, at 22:23, Sven Van Caekenberghe wrote: >>> >>>>>> Do you have a pointer to Philippe's presentation ? >>>>> >>>>> http://www.slideshare.net/esug/esug-unicode >>>> >>>> Thx, reading... >>> >>> You probably mean then that proper (locale aware) collation (sorting), >>> equality (including normalization) are not implemented on WideString ? >>> >>> Sven >>> >>> >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > >
