Changes between Version 6 and Version 7 of AutoEscape alternative

Timestamp:

Apr 18, 2007, 3:30:20 AM (17 years ago)

Author:

Chris Beaven

Comment:

less strawman-y :P

AutoEscape alternative

@@ -1 +1 @@
 = AutoEscaping Alternative =
 
-The current AutoEscaping proposal has met arguments on several fronts:
-
- * Too magic
- * Too implicit
- * HTML escaping only
-
-This alternative proposal attempts to provide a concise solution that answers these arguments:
-
-== Suggested Solution ==
-
-Escaping only matters for !VariableNodes (`{{ object.name }}` tags). A filter is usually applied to each of these nodes.
+Escaping is important for !VariableNodes (`{{ object.name }}` tags). A filter is usually applied to each of these nodes.
 The straight-forward solution is to provide a block tag which can automatically add filters (for html escaping, `|escape`) to any variable tag defined within the block.
 
@@ -20 +10 @@
 To avoid unwanted double escaping, if a tag explictly already uses a filter declared in `finalfilter`, it will not be added again.
 
-== Not too magic ==
+== Keep it Simple ==
 
-There is no magical code hidden underneath deciding on what should be escaped. All that's happening is one or more common filters are being applied automatically to every variable tag defined within the `finalfilter` block.
+There is no complex code hidden underneath deciding on what should/shouldn't be escaped. All that's happening is one or more common filters are being applied automatically to every variable tag defined within the `finalfilter` block.
 
-== Not too implicit ==
+== Explicit is good ==
 
 The template author has to use `finalfilter` explicitly. It ''does'' work across `{% extend %}`ed pages however, but some amount of implicitness is required for this to be a useful tag.