This allows us to override broken encoding detection for Java
properties in translate toolkit.

This causes not needed reordering of translated files (issue #112).

The counting needs to include only units we store in database and
is always expected to start from 1. This "automatically" worked
for po files, where first unit is always not translatable (header) and
thus was skipped.

Fixes issue #111

Some storage backends such as properties or PHP files do not
correctly export source/target values. Let's workaround this by
parsing their internals.

This should fix OS X strings support (issue #107).

This file should not be under version control, having just example there
is enough.