Carl Youngblood wrote:

> I think a better solution if you wanted something like this would be
> to alter rails so it changes the variables in the @post object before
> displaying them.

No, something like this should be done at the template level. If I need 
both the escaped and the unescaped string or want to apply some 
processing to the string in the template it's getting very ugly.

I'm surprised that there is no easy way to deal with this issue; after 
seeing all these examples with date types being automatically displayed 
as a selection form etc. I would have expected Rails to take care of 
properly escaping simple strings.