[Seaside] Seaside and other language than english

[raymondasselin at sympatico.ca]

Hi Ian and Julius

> Wouldn't that be WAHtmlBuilder>>encodeText: instead of 
> WAHtmlRenderer:encodeText?

Yes it is

> The Smallblog Seaside application doesn't seem to be using encodeText: 
> at all but French accents display correctly (at least in my Western 
> European setup) as entries seem to be displayed as entered (i.e with 
> 8859-1 encoding in my browser setup).
> 
> Ian.

I think you are right Ian,  
       when I received your note  (this one)  I reset everything to normal (I mean to the original
Seaside code) but keeping the changeset of Andreas and with the MacRoman encoding in my
Browser everything seems fine for now.   My fault was that I didn't see that my Browser
encoding wasn't set to MacRoman.

Julian whrote
>This is the problem with changing #text: to do encoding by default. 
>I've argued for quite some time that #text: needs to do encoding and 
>that we need #rawText: or #html: or #markup: that you can use in the 
>rare cases where you don't want the encoding.  #encodeText: is just far 
>too long and obscure sounding for the default interface.  The problem, 
>as you've discovered is backwards compatibility - all kinds of code 
>already outputs entities and html tags using the #text: method.

Does I must understand that if we do encoding in Seaside we don't need to
set the encoding of the Browser we use ?  And that doing this we have problem with non
breaking spaces because these were encoded instead of using #rawText: for them (I
understood that #rawText: is a suggestion) ?

>Incidentally, non breaking spaces are also useful in titles and are 
>essential when displaying empty table cells, otherwise most browsers 
>won't display the borders and backgrounds you've given the table (yay 
>browsers!!).

>Julian
Thank to both of you.
Raymond