anchor.diff:  - 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 use django cache subsystem.
  -
  -
  -
  -User guide
  -----------
  -
  -Installation
  -~~~~~~~~~~~~
  +- Django 1.8 support out of the box.
  +
  +
  +=== Django 1.8 support
  +
  +Django 1.8 introduces multiple template engines support and comes with Jinja2 backend.
  +
  +But it has some drawbacks:
  +
  +- not autoloads template tags.
  +- by default search templates on _jinja2_ directory instead of _templates_ (jinja2 are also templates,
  +  I don't understand why put them in different directory?)
  +- not setups i18n support.
  +- not has support for django context processors.
  +
  +In summary, for make it working like _django_jinja_ is already working for years, it requires a lot
  +of boilerplate.
  +
  +*django-jinja since version 1.1 also comes with django 1.8 compatible backend*, but supporting all
  +the things.
  +
  +
  +== Requirements
  +
  +- Python 2.7, 3.3 or 3.4
  +- Django 1.5, 1.6, 1.7 and 1.8
  +- jinja2 >= 2.7.0
  +
  +
  +== User guide
  +
  +=== Installation
   
   The simplest way to install **django-jinja** is using **pip**:
   
  
positive.code: )
  ----
  
  Add add it to django installed apps list:
  
  [source, python]
  ----
  INSTALLED_APPS += ('django_jinja',)
  ----
  
  django-jinja template loaders inherit's from a django template loaders and works like middleware, intercepts
  by predefined condition templates for render with jinja2 engine.
  
  The simplest condition is using file extensions:
  
  
negative.code: ----
  
  
  ==== Additional settings
  
  If you need more low level customizations for jinja2 engine, *django-jinja* exposes
  `JINJA2_ENVIRONMENT_OPTIONS` settings for it:
  