anchor.diff:  ----
   TEMPLATES = [
       {
  -        "BACKEND": "django.template.backends.django.DjangoTemplates",
  -        "DIRS": [],
  -        "APP_DIRS": True
  -    },
  -    {
           "BACKEND": "django_jinja.backend.Jinja2",
           "APP_DIRS": True,
           "OPTIONS": {
               "match_extension": ".jinja",
           }
       },
  +    {
  +        "BACKEND": "django.template.backends.django.DjangoTemplates",
  +        "DIRS": [],
  +        "APP_DIRS": True
  +    },
   ]
   ----
   
  -
  -All other options are passed directly to environment constructor.
  +NOTE: Is very important the order, because the django-jinja backend uses the same directory for the
  +templates and acts as a middleware, if you put the django engine first every jinja template will
  +be found by the django engine.
  +
   
   === Advanced options
   
  
positive.code: 
  == Known Issues
  
  - django-jinja does not works properly with django's `TemplateResponse` class, widely
    used by generic views. My recommendations is subclass the `TemplateResponseMixin` and
    overwrite the render_to_response function.
  - Previously to django 1.8, some way of using i18n related functions are not properly
    parsed with makemessages.
  
  
negative.code:     ],
  }
  ----
  
  As usual, this is a default list of context processors and you can forget
  setup them if you do not have own. Furthermore, it is now not recommended way
  to setup variables in the context and the purpose of its existence is a help
  for migrations.
  
  
  ==== Custom filters, globals, constants and tests
  