Localisation updates from http://translatewiki.net.

Change-Id: I545a549bc2cf4c6194cbbae92022a28f57132688
Make sure that only SQLStore tests run on a SQLStore

These tests should actually use a MockStore but since I don't have time to
fix this right now and as a temporary measure those tests are bound to
use the SQLStore only.

Change-Id: Ic49d5d829f3db9c764729ca4647cfbc5bbe44be0
Add tests in response to 54967

Tests don't show any unusual behaviour as claimed by the bug.

Bug: 54967
Change-Id: Ib1128f81c8c0a9a36355e70b39b647c5ab4f1607
Localisation updates from http://translatewiki.net.

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

Change-Id: Ibbcb450bd5d27715c39ce38095c61c031859ef66
\SMW\SemanticDataSerializer

Code coverage: 100%
CRAP: 34

A full qualified serialization of a SemanticData container. Tests include
rountrips for various scenarios. The data model is described in
/serializer/README.md.

Change-Id: Ief0648e3ca70f9f815139e51528a1bc695bad1fc
Add QueryResultTest, improved DISerializerTest

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

Change-Id: I97ff3b6c88b354e6988ebc0c1af223ab9fb46d54
Switch SMW\SerializerInterface with ext-Serialization Serializer/Deserializer

Replace SerializationInterface with the ext-Serialization interface without
implementing any strategies. Re-factoring can be done at a later stage without
the need to change the public interface.

Change-Id: Iddf4ece627f086efe9ce3e68085b4a638e055f91
\SMW\DISerializer is in fact a \SMW\Serializers\QueryResultSerializer

DISerializer was never a "real" DI serializer and only used to
serialize QueryResult objects.

We also don't want to expose any specific method to the "outside world"
and instead have the SerializerFactory manage the SerializerInterface.

Change-Id: Ie234128e5ae7f0c72e619837cabdddb786958674
Field "serializer" only to be invoked on top

Change-Id: I116f70f9322120a9068d4ea86f11e51ec9b468a7
Merge "\SMW\DISerializer is in fact a \SMW\Serializers\QueryResultSerializer"
Localisation updates from http://translatewiki.net.

Change-Id: I8f75b495efac3166e6ef40857bcf75063a546657
Merge "Localisation updates from http://translatewiki.net."
Fix PHP_CodeCoverage_Exception on QueryResultSerializer

Change-Id: Ibcb647231da063ee2bf4bc99247f459ad4909c96
Simplify SemanticData subobject serializer/deserializer

Change-Id: Ia007ed92ef938d277179c56f7f903995c3561795
\SMW\ApiBrowse enables to browse a subject via api.php?action=browse

Code coverage: 100%
CRAP: 22

This is the corresponding Api for the Special:Browse interface (without
support of incoming properties).

In order to work with the Api, the following schema [2] can be used.

- Uses the new SMW\Serializer [1]
- JSON and XML output are supported

[1] https://gerrit.wikimedia.org/r/#/c/89098/

[2] api.php?action=browse&subject=Main_Page

Change-Id: I00c2fab386d0c74ef0b576876edb2f873c17bfde
\SMW\ContextAware + SMW\BaseContext

Making an object ContextAware allows to inject objects that depend a
context rather than directly linked to the DIC and it also enables support
objects to be accessed on requests rather than during instantiation.

Depending on a context (base, mock etc.) will give full control over the
object life-cycle as the context internally represents the current invoked
 DIC and with it its available object definitions while when changing to
an object definition is necessary it is done in only one place, the
DependencyContainer.

Instead of injection a builder directly through a constructor, we will use
the context as a single representative to carry out the responsibility
to enable access to a builder and its definitions.

## Notes
http://accu.org/index.php/journals/246

Change-Id: Ib6fce6d34f0b9101d4781cde0dd5fe268d30605c
Update 1.9 release notes (needs re-work)

Change-Id: I3a2e059c7ff195fc9c02605b59b093c3d28b72aa
Namespace fix

Change-Id: Ia2000c93a4688a442d821933920d0d2cbf3f297f