added a comment - - edited
What a tedious job
"phpunit AllTests.php | grep \'fi | wc -l" returns 22 atm.
I did this for 1.10.7. How dynamic these message templates really are? Am I supposed to fix this many keys in translation file between every minor release, only because the English template was modified? Wouldn't it be better if the keys were "real" template keys e.g. 'ipInvalid', 'notIpAddress', etc.
For example what's the value of this kind of changes:
"Invalid type given, value should be a string"
=> "Invalid type given. String expected"
In my opinion this is not any better English, only marginally shorter and as user friendly as the previous one. Some of the changes were reasonable for example
"Luhn algorithm (mod-10 checksum) failed on '%value%'"
=> "'%value%' seems to contain an invalid checksum"
which is much more user friendly.
So let me ask. What's the real purpose of these translation files? Straight translations for English ones, giving more information for developer or not straight ones being more user friendly. In production, I'm using much simpler translations to achieve better user experience, but here I thought that the straight translations fit better in ZF resources. It's not easy to serve both purposes from one resource file. Refering to the discussion in #zftalk.dev... Swedish resource file has been erased, because it was complained not to be Swedish. I think that it is as much Swedish as my Finnish resource file is Finnish. It is the language what developers tend to write in their error messages.
The attached resource files adds 33 errors. Please solve these 33 errors so we can add it to our core. See "resources/AllTests" for details on the failed tests for the language "fi"