Localization update#588
Conversation
|
Why change the copyright year? On one hand the script itself didn't change and therefore there is formally no need to update the claim as there is nothing new to claim. And in general only the beginning year was of importance.
Which changed recommendations and how projects adjusted: Personally I would drop that specific change, but that call is up to jaromil. And it shows that we need to change something in regards on how to handle translations and the workflow :D |
|
Reverted copyright year change. I liked the idea of the GitHub Action in PR #557 |
|
I'll let you decide when to merge this @Narrat since you are more busy on the translation front. |
|
Reverted copyright year change in |
|
Then it may be better to merge this sooner than later. Before new features or bigger changes get merged and the diff gets even bigger. |
tomb.pot(recreated usinggenerate_translatable_strings.pl);pt_BR.potranslation (updated to new tomb.pot, by merging, and revised a few translations to be more accurate).