[Seaside] Re: no HTML entities for 8bit characters in UTF-8 encoding

[Colin Putney]

On Jun 28, 2004, at 12:51 PM, Avi Bryant wrote:

> Why?  I agree with you entirely on what the code should look like in 
> the model.  It's just that you're picturing #youHaveKnives: returning 
> a string, whereas I'm picturing it returning an object that responds 
> to #localize.
>
> Why?  For one thing, think about the halo possibilities.  If the 
> renderer is getting passed static strings, all it can ever do is dump 
> them out as HTML.  If it's being given localization objects of some 
> kind, it can get switched into a mode where it renders text inputs or 
> edit links for each localizable string.  Or it can collect all the 
> localized strings on that page as it renders them, and provide a link 
> that brings up a separate editor for just those strings.

Ok, now I get it. The Localization call returns an object that is 
opaque to the model, but can be dealt with intelligently by the views. 
String has a default implementation of #localize so non-localized apps 
can still use string literals and won't know the difference.

Sounds good.