On 19 Jun 2006, at 20:18, [EMAIL PROTECTED] wrote:
> The biggest downside is if you want valid HTML data stored for one > output > type and escaped for another. But this is not a scenario I've ever > seen > in the real world, and regardless is easily worked around with simply > returning to CharFields for that one attribute. (and manually > escaping of > course) > > What do you think? I'm not keen on escaping being controlled by the model - escaping should be a template-level decision as that's when you decide what format is being output (plain text email / HTML / XML / LaTeX for PDF conversion etc). I played around with some proof of concepts over the weekend and I think I have some ideas that should keep most people happy. I'll try to write them up on the wiki this evening. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
