Two of these strings were not a fix, just a removed string, so no need for pofix.
The other was not specific enough for pofix to match unambiguously.
Also, someone forgot a comma somewhere, causing a syntax error.
(cherry picked from commit 4331c7f4e90dc62a6ea0551abbe971261e7526e7)
That comma wasn't supposed to be replaced with a period, and I didn't
notice the mistake before pushing the commit.
[ci skip]
(cherry-picked from commit 20bfb35bdda3dca06a9e997812d50bea0e24f341)
The tool that generates .po files splits lines in order to limit line
length, and pofix can't track split strings. Thus, pofix search rules need
to be shorter so that pofix finds the affected strings.
I also moved the replacements to the right text domains, placed wesnoth-l
to the right spot, and removed the "Asheviere is the Queen of Wesnoth"
replacement because it isn't pofixable. (The second part of the string
becomes just "Queen of Wesnoth." and "queen of Wesnoth." with lowercase Q
is used legitimately elsewhere.)
[ci skip]
(cherry-picked from commit 3df91c9fc126ac3fd70ab9c0ea9e97eb3d008b33)
Otherwise people will keep complaining that it doesn't reflect the
latest 1.14 version since the original number was valid for 1.14.0 and
1.14.4.
[ci skip]
(cherry-picked from commit c589e39098614b2180b4043db6b9faa71afe6c84)
Also fixes a mistake from the 1.14.3 rules that caused "xxx MiB" to be
replaced with "xxx MB MiB" for all platforms. Oops. Nobody noticed
anyway (?).
[ci skip]
(cherry-picked from commit 12a3b973b9f357d0b1685df5b29fbcea0fefc7be)
NOTE: the rule for the "true orc" case does not work. The string in
question will just have to be fuzzied.
[ci skip]
(cherry-picked from commit 72948787450d2ba273b9a901455ae02ccf1cce5e)
This reverts commit 4d5a3de4e63ebaac4a853b0f724d1d342d451dd0.
Restoring correction at @Vultraz's request.
[ci skip]
(cherry-picked from commit e161d59536452ca78897d92cb2eaae2099228075)
Two of these strings were not a fix, just a removed string, so no need for pofix.
The other was not specific enough for pofix to match unambiguously.
Also, someone forgot a comma somewhere, causing a syntax error.
(cherry-picked from commit 3768dc687d9f8a709243912f7388f2917d20e2db)
This reverts commit fb866c6d1310d8398f0f481a8ab16b1606286cdd.
This fix is specific to master and translators aren't supposed to be
touching master at this time. There is no point to its existence.
(cherry-picked from commit 4d5a3de4e63ebaac4a853b0f724d1d342d451dd0)
