This will enable the creation of Django formated translation files as described here: https://docs.djangoproject.com/en/dev/topics/i18n/translation/
We now ignore the current directory and its parent as neither of these are meant to be checked in write_all_files. This could cause extra files to be written unexpectedly.
This fixes issue #40
It's valid for a msgstr to be broken over multiple lines, all of which are enclosed with ". To handle this, no longer iterate over the lines within an item but rather apply the matching to the entire item.
We used to only write translations to the strings file that did not match the developer language. It was done this way to try and reduce space in the strings file and to get en-UK to pick up en changes. This turned out to be the wrong decision. It's better to explicitly ensure that all strings are translated in all languages, and to not automatically pick up en string changes in other languages. This fixes issue #29.
…ification The proper comment structure for gettext is not ".#" but "#." as seend in: https://www.gnu.org/software/gettext/manual/gettext.html#PO-Files The code was updated, but the test case was not. This commit addresses that oversight.
…ging We don't distinguish between the types of comments and should allow space between the field type and the value. Also, the extra logging was accidentally left in and should be removed
It was written ".#" but should have been "#." for extracted comments
Twine would crash if --tags were supplied on the command line. This parameter is undocumented for consume-string-file. It shouldn't do anything (at least not yet). Fixes #23