On Tue, May 6, 2008 at 10:45 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > On Tue, May 6, 2008 at 8:21 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote: > > > > Yeah, we probably should mention this in the docs, along with an > > explanation of how to enable Markdown's safe_mode. Sure, it's > > explained in the source, but the other markup filters don't offer any > > extra features so I doubt most people even look unless they encounter > > a problem. > > > Also, with 1.7, django trunk makes safe mode either True or False, but > markdown takes three values (replace, escaped, remove) and True > equates to replace. >
I've given that some thought and I'm not sure how to approach it. Truth be told, I never cared for that API change (passing in one of three possable strings), but we wanted to keep some backward-compatability and definitely wanted the 'escape' feature, so in it went. Not sure how to pass that on from the django filter though. Any suggestions? -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
