Merge branch 'release/v0.2.3' into develop
remove fuzzy flag from string

we want to filter those, soon. A fuzzy message will be added with the
tests for the new feature
filter messages marked as fuzzy from catalog by default

translators mark messages as fuzzy, if there is a problem with the
translation. Those messages need review and are most likely wrong. In
production environments, messages marked as fuzzy should not be
deployed, so these messages should be filtered out. Implementations can
than use the fallback translation (which might be the untranslated
string).
add the includeFuzzy option for compile_po tasks

sometimes messages marked as fuzzy should be included into the catalogs.
The includeFuzzy option can be used to do so.
update dependencies

next release will use up-to-date libraries
bump version and release history
Merge branch 'release/v0.3.0'