Paradatabase:Before work/de

Es gibt grundlegende Konzepte, die bei der Arbeit an einem Projekt berücksichtigt werden müssen.

Technische Informationen

Zum erforschen der Tools und Funktionen nutze die HauptseiteMediaWiki. Es gibt viele Links in der linken Seitenleiste, sowie ein ziemlich effektives Suchfeld in der oberen rechten Ecke.

- es kann sinnvoll sein, eine separate Liste der Quellen zu erstellen. In der Zwischenzeit kannst du sie hier hinzufügen."

Namensräume

Namensräume werden verwendet, um Informationen nach Zweck zu unterteilen. Beispielsweise sollten Informationen für Besucher von Informationen für Entwickler getrennt werden, was wiederum eine Trennung in Service-Informationen und Handbuch bedeutet. (Verwechsle Namensräume nicht mit Kategorien)

Ein Namensraum wird der Seite zugewiesen, indem sein Name mit einem Doppelpunkt vor dem Seitennamen hinzugefügt wird (Help:Namespaces = die Seite Namespaces im Namensraum Help). Liesmehr Help:Namespaces undManual:Namespace.

Es gibt eingebaute (Standard-)Namensräume: Media, Special, (empty), Talk, User, User talk, Project, Project talk, File, File talk, MediaWiki, MediaWiki talk, Template, Template talk, Help, Help talk, Category, Category talk. Der Namensraum Project, Project talk in unserem Projekt haben die Aliase Paradatabase, bzw. Paradatabase talk.

Zusätzliche Namensräume in unserem Projekt: Manual, Manual talk, Forum, Forum talk

Zur Vereinfachung werden die folgenden Aliase hinzugefügt. "Paradatabase:" hat den Alias "Pdb:", "Manual:" - "Man:", "Forum:" - "FM:". Somit sind "Project:Project tasks", "Paradatabase:Project tasks", "Pdb:Project tasks" die gleiche Seite.

Weitere Namensräume und Aliase werden vom Projektleiter genehmigt.

Es ist notwendig, dass sich jede Projektseite in dem Namensraum befindet, für den sie angelegt wurde.

Die Verwendung eines Präfixes mit einem Doppelpunkt, der nicht den vorhandenen Namensräumen entspricht, muss zwischen den Entwicklern vereinbart und vom Head genehmigt werden. Um herauszufinden, welche Namensräume in einem Projekt vorhanden sind, verwenden Sie Special:Search oder Special:ApiSandbox mit Abfrage action=query & meta=siteinfo & siprop=namespaces

Diskussion

Verhandlungen über den Inhalt einer beliebigen Seite werden auf der entsprechenden Registerkarte 'Talk' der Seite geführt.

Fragen, die sich nicht auf den Inhalt der Website beziehen, nicht ausgearbeitete Fragen, Probleme, Abklärungen, Ideen sollten im Namensraum "Forum: " platziert werden.

Alle Diskussionsteilnehmer müssen sich an die Diskussionsregeln halten.

Nachrichten-Feed

Wichtige Neuigkeiten, Ereignisse, die die Entwickler des Projekts betreffen, sollten kurz auf der Seite Pdb:News feed berichtet werden.

Fragen- und Problem-Feed

Questions, problems concerning all developers should be put on the page Pdb:Questions-and-problems feed, and then brought up for discussion in the "Forum:". The same applies to the important issues for which you can not find the answers in MediaWiki, Google, Yandex.

Multilingual Paradatabase

Multi-language support in Paradatabase is one of the most difficult but very important tasks. This will significantly expand the audience and make information about paragliders more understandable for those who do not speak English.

To learn more read Multilingual MediaWiki

The translation model is organized as follows.

English is the primary language. This is the language of the content and the name of the original page. Translation is carried out by project participants using the Translate extension. In order to activate the translate function, one must have the appropriate rights and prepare a page for translation. Details for those who are having access to this function can be found in the documentation Extension:Translate

The Pages translated into other languages have a name consisting of the name of the source and the language code with a slash. For example, the main page is "Pdb:Project tasks". Translation into Russian - "Pdb:Project tasks/ru", translation into French - "Pdb:Project tasks/fr".

Only source text can be corrected in the standard way on the tab "Edit". Translations are being corrected on the "Translate" tab by Extension:Translate.

The translation of the title of the page, which is not the source, into another language is possible, but its name and the link to it remains English. For example, the "Project tasks/fr" page will have the title "Tâches du projet". To facilitate its search by users who do not speak English, should be created a new page "Tâches du projet" and set the redirection to "Project tasks/fr". To redirect the page its content should be the only line:

#REDIRECT [[Pdb:Project Tasks/fr]]

Creating source text in your language

If the page does not require translation (this should be a rare exceptional case), then you need to create a page in your language and assign it the language using Special:PageLanguage, which can be accessed by clicking the Page Information link in the left sidebar and finding Page content language row in the table. If the language change is not available, you need to contact the administrator.

We must distinguish the page Name from the Title. By the page Name we navigate while the page Title is a part of the content. In the case when the page does not require translation, the name and title match.

In case a translation is required, the page name does not depend on the language of the original page and must be in English. The title can be translated into another language.

Manual: Translate/Page translation administration

Tools:

• Special:PageLanguage
• Special:PagePreparation
• Special:Translate
• Special:PageTranslation

For example, the page "Elpmaxe txet Niradnam" has been created. To translate it you must use the following algorithm:

1. Create a page with the English name "Mandarin text example".
   Its language does not change. It must be English.
2. Insert there the English translation or at least a short phrase that says that it need a translation.
3. Prepare the text for translation using Special:PagePreparation, (or, in special cases, manually add the tags <languages />, <translate></translate>), open it again and click on "Mark this page for translation".
4. By the link “Translate this page”, translate into Mandarin the title “Mandarin text example” and all the text using the original from the page "Elpmaxe txet Niradnam" created at the very beginning of the example.
5. Make sure that the English version of the page "Mandarin text example" and the Mandarin "Mandarin text example/md" exist and correspond to the desired texts.
6. Go to the "Elpmaxe txet Niradnam" page and replace the page content with #REDIRECT [[Mandarin text example/md]]
7. Check out the links to the "Mandarin text example" and its translation in the Search box.

Corrections of such a page must be started from the original page in English. In case of a poor knowledge of English, you need to consult with someone who knows English well, or use a template:

{{qst | source language code | text to be translated}}

After correcting the source text the operation "Mark this page for translation" should be repeated. For corrected fragments, that do not affect the content of the translation, the checkbox "Do not invalidate translations" can be checked.

The third variant. There are several texts about the same in different languages but not a 100% translation of each other. They can be changed but it does not require synchronism of changes in other texts. In this case each of these texts is created as text in its own language, but it is necessary to place a language switch at the beginning of the page, for example:

{{LangSwitch|'''English''' * [[Special:MyLanguage/Pdb Annonce/fr|français]] * [[Special:MyLanguage/Объявление о создании Пбд|русский]]}}

Groups of users

When working on a project, the main principle is trust, which is necessary to provide developers with the greatest opportunities. It is assumed that any participant has good intentions and wants to do everything in his power to help the project. If the participant creates problems for the project, then the issue of his exclusion will be raised, because coherence and the principle of the maximum set of possibilities will be threatened.

We need to assign the roles of the participants by creating the appropriate groups based on these considerations. In the course of work we will select the optimal sets of rights. Now, when there are few participants and the roles are not worked out, contact the administrator for additional rights or put a request in Pdb:Questions-and-problems feed

Note for translators

It is more convenient and safer to first translate text in a text editor, such as Notepad ++ or MS Word, looking at the source text or copying the source text into the editor. And then when translating through "Extension:Translate" insert text fragments by the clipboard. There may be a mismatch of the source text with the text in the translation window, if there were any corrections, but you do not need to pay attention to this.