tree 2c2e6b5cd25542b3160a20a9ac9c926f1a30dcf6
parent 72e95faf46665753247796df7403c3b49bfe092d
author Roman Imankulov <roman.imankulov@gmail.com> 1444736658 +0000
committer Roman Imankulov <roman.imankulov@gmail.com> 1444753567 +0000

Ensure babel i18n extactor works properly with non-ascii input

If mako templates contain something like "_('Köln')", babel extractor converts
it to pure ASCII so that resulting .po file would contain "K\xf6ln". Not all
translation tools and translations are ready for such kind of escape sequences.

Babel allows message ids to be non-ascii, the plugin just has to return Unicode
objects instead of ASCII strings (and that's exactly how Babel built-in Python
and JavaScript extractors work).

This fix ensures mako extractor doesn't excape non-ascii symbols, works well
both for Unicode and non-unicode input (there is a test for cp1251 encoding),
and also provides a workaround for babel charset detector python-babel/babel#274.