[Seaside] Re: Encoding problem

[Paul DeBruicker]

On Pharo 1.4, with Seaside 3.1, there is no error.

I have not tried with Pier loaded.  Should I?






Johan Brichau-2 wrote
> What version of Seaside are you guys running?
> 
> On 20 May 2014, at 13:19, Sven Van Caekenberghe <

> sven@

> > wrote:
> 
>> 
>> On 20 May 2014, at 12:47, Stephan Eggermont <

> stephan@

> > wrote:
>> 
>>> We have an issue in default Pier with rendering/encoding.
>>> Did I miss setting encoding somewhere?
>>> 
>>> If we enter in WAEncodingFunctionalTest the following three characters:
>>> ->ë
>>> the text input field removes the -.
>> 
>> I can confirm the problem. This is really weird.
>> 
>> Apparently you need a non-ascii character preceded by an xml-unsafe one:
>> 
>> abc
> <é
>>
>  aaa&ç
>> 
>> And when the characters are printed one by one wrapped in a span they all
>> show !
>> 
>>> We noticed because the text area used to edit pier documents
>>> became unusable.
>>> 
>>> Stephan
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> seaside mailing list
>>> 

> seaside at .squeakfoundation

>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
>> _______________________________________________
>> seaside mailing list
>> 

> seaside at .squeakfoundation

>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> _______________________________________________
> seaside mailing list

> seaside at .squeakfoundation

> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside





--
View this message in context: http://forum.world.st/Encoding-problem-tp4759665p4759711.html
Sent from the Seaside General mailing list archive at Nabble.com.