Because there’s more than one person involved in writing code. Each person has its own preferences on how to write code, this applies not only to translatable strings. And then … well, when writing code, using elegant language in texts isn’t exactly top priority. Code writers watch out much more for the code doing what it should do.

That said, if you find such mismatching use of human language, don’t hesitate to report them as code bugs (on Github). Changing such wording doesn’t change how the code works, so it’s easily replaceable.

Because there’s more than one person involved in writing code. Each person has its own preferences on how to write code, this applies not only to translatable strings. And then … well, when writing code, using elegant language in texts isn’t exactly top priority. Code writers watch out much more for the code doing what it should do.

That said, if you find such mismatching use of human language, don’t hesitate to report them as code bugs (on Github). Changing such wording doesn’t change how the code works, so it’s easily replaceable.

Nice try, but we’re talking about translation items imported fom PrestaShop which have been messed up since years. And already in 2013 Francois and I had prepared a handout for the developers in order to harmonize the wording or at least the spelling. But things changed not until PrestaShop engaged a person reponsible for this with the authority to decide how the translatable strings had to look like.
What we are dealing with here is to large extend a burden of the past!

“There is always a well-known solution to every human problem—neat, plausible, and wrong."

Pl, don’t worry. Most of sentences are ok.
I’ve been worrying more about some sentences which are same in english, but has different translations in Russian, depending on context.
Fortunately, there’s very few of such issues.