Two <BLANKLINE> in generated PO EOFs

[mondeja]

As is documented, write_po function renders two blank lines at the end of the file. GNU gettext documentation about PO files does not specify that this is mandatory.

I think that this makes no sense, but maybe something could explain why this has been the choice. It creates inconsistent output in diffs, uneeded extra space in disk, and so on... it is just a bad practice for text files.

[akx]

Each message is followed by a trailing newline:

babel/babel/messages/pofile.py

Line 617 in 96acf86

_write('\n')

It's easier to just print one rather than try to figure out when we're printing the last entry and elide the trailing newline.

Patches welcome, of course :)