Mediawiki download as pdf online

GitLab: project page git repository URL [ help ] commit history Note: No localisation updates are provided by translatewiki. Added rights.

Hooks used. Hidden categories: Pages using deprecated source tags Extensions without an image Extensions without a compatibility policy Extensions with manual MediaWiki version Extensions not in ExtensionJson.

Namespaces Extension Discussion. Views Read Edit View history. See task T for more information. Subscribe to our release announcements mailing list. In such a case you can simply download more - increase the depth value - or all revisions later, or make a fresh shallow clone.

Namespaces Page Discussion. Views Read Edit View history. Bug tracker Code docs Code repository Statistics. Add links. What is MediaWiki? It can be extracted on most operating systems without installing any additional software, and is generally recommended for Windows users.

We also provide a tarball tar. It is advised not to use 7-Zip to decompress the tarball. Archive Utility can be used instead. Because MediaWiki is licensed free of charge, there is no warranty, to the extent permitted by applicable law. MediaWiki requires PHP 7. For more information, please read the pages on system requirements and compatibility.

Active MediaWiki developers should instead download from Git to get the latest version of the MediaWiki software. At this point, an automatic Travis script is executed and what it essentially does, is that it makes the Django service dump its database into XML format to the Git project, commit the possible changes and push them to the master branch. If the dictionary has been modified in the Mediawiki side, the person developing the XML files has to resolve the conflicts using Git.

Because resolving conflicts is what Git is really good at, leaving the conflict resolution to that system makes our system easier to develop and maintain as we can safely assume that Git is stable enough. Once the pull request is finished and all the conflicts are resolved, the Django based system will be notified about the changes in the master branch and it will start to update its own database and Mediawiki. Another challenge for this system is the different data structures used.

XMLs have their own formatting, the Django services internal database uses Mongo which is essentially a JSON based data structure and finally Mediawiki shows its pages using its own Wiki syntax.

The Django services data structure cannot be identical with the XMLs for two different reasons: first of all, even Skolt Sami has multiple different XMLs with different structures and secondly we aim to support multiple languages and make the process of integrating new languages an easy one.

Thus far, this has seemed to work well when the Ingrian XML files were added to the system. The system also needs to be easy to use for non-technical people. From people working directly with the XML files, you can expect that they know how to maintain the structure of the files, for example that every open tag has to be closed in the correct order and so on. However, from people dealing with the Mediawiki based dictionary, you cannot expect them to understand how the Wiki page needs to be structured in order for the Django service to understand it correctly.

That is why when a user enters the page edit mode on Mediawiki, a form is displayed instead of the raw Wiki text. The same Java Script is used by the Django service when it updates the pages on Mediawiki. Before this project their Mediawiki platform already had one dictionary, Ludic, and the Finnish WordNet. Since multiple parties are interested in the same platform, it only makes sense for us to use it as well.

This opens the possibility of in- terlinking dictionaries from different providers to enhance the quality of all of them. From the point of view of our project, the Mediawiki dictionary serves two pur- poses.

People with editing rights can edit the dictionary easily online and other peo- ple can access an up-to-date dictionary for Uralic languages for free. The Mediawiki infrastructure also allows for variation in the extent of editing rights. This means that, while there are two different kinds of user groups whose needs have to be taken into account, there is also a possibility for monitored editing by a larger and larger contributing group of users.