anchor.diff:  
   [NOTE]
   ====
  -If you are using the default value for app templates directory for
  -django-jinja backend, take care to the template engines order, because the
  -django-jinja backend by default uses the same directory for the templates that
  +If you are using the default value for the app templates directory of the
  +django-jinja backend, take care of the template engines order, because the
  +django-jinja backend by default uses the same directory for the templates as
   the django template engine. If you put the django engine first every jinja
   template will be found by the django engine.
   ====
  
positive.code: {% endtrans %}
  ----
  
  Additionally, django-jinja extends the django's `makemessages` command to make it work
  with jinja2 i18n tags.
  
  If you want more django like i18n related tags, you can use extensions from
  https://github.com/MoritzS/jinja2-django-tags.
  
  
  === Replace jinja filters with django versions
  
  Django and Jinja overlaps in a little subset of template filters. For handle proper this, django-jinja
  gets the decistion to use the jinja versions. But if you want a django version of them, you should use
  the "django_jinja.builtins.extensions.DjangoExtraFiltersExtension" extension.
  
  The affected filters are: title, upper, lower, urlencode, urlize, wordcount, wordwrap, center
  
negative.code: - I18n subsystem adapted for Jinja2 (makemessages now collects messages from
    Jinja templates)
  - Compatible with python2 and python3 using same codebase.
  - jinja2 bytecode cache adapted for using django's cache subsystem.
  - Support for django context processors.
  
  
  