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.

Sven

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
> 


Reply via email to