Fix/Update translations

[corubba]

Fix update_translations.py

The resource must be imported so shortcuts and menues can be read.
parse_menus is unsed, they are read in parse_shortcuts too.

Update translations.py

The pylupdate5 only gathers translation keys from python sources, and not from the menu/shortcut files in data. To still make it work, update_translation.py exists to read these data files, extract their translation keys and insert them into translations.py as code. That way pylupdate5 will pick them up and properly update the .ts files.

$ ./update_translations.py de

Compile translations

The .qm file are a binary form of the .ts file, that is used during runtime.

$ lrelease translations/*.ts

Regenerate resource.py

All data files including compiled translations are not read directly from the filesystem during runtime, they are provided by the Qt
resource system. So for updated translation to actually be used, you have to regenerate the resource.py too.

$ pyrcc5 puddlestuff/resource.qrc -o puddlestuff/resource.py

[sandrotosi]

the change of course look good

i'm wondering about the value of keep requiring the language argument to update_translation.py -- should we just make it update all languages (in particular when changing strings in the code)?

[corubba]

Yeah, I know what you mean. Thought about this too, and came to the conclusion to make it optional in the future: If you don't provide it, update all languages; If you provide it, create the translation files (if needed) and update all languages (or maybe only that language). But the update_translation.py needs a bit more refactoring to achieve that, this PR is just to get it in working order and the translations into a consistent state to make the diffs on the translation files useful (and somewhat document which hoops you have to go through to actually update translations for endusers).

[sandrotosi]

Yeah, I know what you mean. Thought about this too, and came to the conclusion to make it optional in the future: If you don't provide it, update all languages; If you provide it, create the translation files (if needed) and update all languages (or maybe only that language). But the update_translation.py needs a bit more refactoring to achieve that, this PR is just to get it in working order and the translations into a consistent state to make the diffs on the translation files useful (and somewhat document which hoops you have to go through to actually update translations for endusers).

cool, glad i'm not alone in seeing that as unexpected, merging this PR now