[Seaside] Encoding problem

[Sven Van Caekenberghe]

Seaside 3.1.0 (ConfigurationOfSeaside3 stable, I guess) on Pharo 3 (Bootstrap).

On 20 May 2014, at 13:53, Johan Brichau <johan at inceptive.be> wrote:

> What version of Seaside are you guys running?
> 
> On 20 May 2014, at 13:19, Sven Van Caekenberghe <sven at stfx.eu> wrote:
> 
>> 
>> On 20 May 2014, at 12:47, Stephan Eggermont <stephan at stack.nl> 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 lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside