Localisation updates from http://translatewiki.net.

Change-Id: I53197dbe482554ca49963f664664607f5d264740
Localisation updates from http://translatewiki.net.

Change-Id: I3768fb01625531080917fc3857141ab9f9f163c4
Localisation updates from http://translatewiki.net.

Change-Id: I4bbe06da84efe5061a6d4f30c666cfbe3df01919
Localisation updates from http://translatewiki.net.

Change-Id: If61db4127b30731dac495a0a87712a1a2283b52e
Localisation updates from http://translatewiki.net.

Change-Id: Ifede59c08f306250177a2ca7d9f148f735f8a829
Correct Banner Over Allocation

When we distribute the remaining slots, because we do not check if
we have over allocated, we could end up with a situation where a
banner that did not need any extra slots got one.

E.g. 3 banners A, B, and C with weight 5, 100, and 100 would allocate
A: 6.66%
B: 46.66%
C: 46.66%

Now they will allocate
A: 3.33%
B: 50.00%
C: 46.47%

Change-Id: I70c6258b52bd1656d0967e45fc4dd74175ee6a57
Localisation updates from http://translatewiki.net.

Change-Id: I1774180f2296a8169f279f42d972a92dcae7339c
Merge remote-tracking branch 'origin/master' into wmf_deploy

* origin/master:
  Localisation updates from http://translatewiki.net.
  Correct Banner Over Allocation
  Localisation updates from http://translatewiki.net.
  Localisation updates from http://translatewiki.net.
  Localisation updates from http://translatewiki.net.
  Localisation updates from http://translatewiki.net.
  Localisation updates from http://translatewiki.net.

Change-Id: I3847c3fde80ff31b45d366eaa90ab32b1c5f92d4