anchor.diff:  explicit calls to callable from templates, has better performance and has a plugin
   system, etc ...
   
  -Django comes with jinja backend, why I should use *django-jinja*?
  +Django comes with jinja backend, why should I use *django-jinja*?
   
   The Django builtin backend has very limited set of features if we compare it with
   the django template engine and in my opion is not very usable because it does not
  
positive.code: {% endtrans %}
  ----
  
  Additionally, django-jinja extends the django's `makemessages` command for make it work
  with jinja2 i18n tags.
  
  If you want more django like i18n related tags, you can use extensions from
  
negative.code: 
  === Context processors support
  
  It is a helper to use django's context processors with jinja2 backend
  for django 1.8.
  
  .Example setup a bunch of context processors:
  