Paradatabase:Before work

To collegues, who know English well, please:

If you see errors, correct them. If there are no errors, delete this request-box

There are basic concepts that must be considered when working on a project.

Technical information

To explore the tools and the engine capabilities main site is MediaWiki. There are a lot of operational links in the left sidebar, as well as a fairly effective Search box in the upper right.

- it may make sense to create a separate list of sources. In the meantime you can add it here.

Namespaces

Namespaces are used to divide information by purpose. For example, information for visitors should be separated from information for developers, which in turn is parting into service info and manual. (Do not confuse Namespaces with Categories)

A namespace is assigned to the page by adding its name with a colon before the page name (Help:Namespaces = the page Namespaces in the namespace Help). Read more Help:Namespaces and Manual:Namespace

There are built-in (standard) namespaces: 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. The Namespaces Project, Project talk in our project have aliases Paradatabase, Paradatabase talk respectively.

Additional namespaces in our project: Manual, Manual talk, Forum, Forum talk

For convenience, the following aliases are added. "Paradatabase:" has the alias "Pdb:", "Manual:" - "Man:", "Forum:" - "FM:". Thus "Project:Project tasks", "Paradatabase:Project tasks", "Pdb:Project tasks" are the same page.

Additional namespaces and aliases are approved by the project manager.

It is necessary that each project page was in the namespace for which it was created.

The use of a prefix with a colon that does not correspond to existing namespaces must be agreed between the developers and approved by the head. To find out what namespaces are in a project, use Special:Search or Special:ApiSandbox with query action=query & meta=siteinfo & siprop=namespaces

Discussion

Negotiations on the content of any page are carried out on the corresponding tab Talk of the page.

Questions that are not related to the content of the site, questions that have not been worked out, problems, clarifications, ideas should be placed in the namespace "Forum: ".

All discussion participants must comply with Discussion rules.

Pages created in the "Forum:" namespace, as well as others, should contain only operational information. For questions, explanations, clarifications use "Forum_talk:". The "Discussion" link of the current page in the "Forum:" namespace is used to go to "Forum_talk:".

News feed

Significant news, events concerning the developers of the project should be briefly reported on the page Pdb:News feed.

Questions-and-problems 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. Herewith the name of each page is in English plus a slash and a language code. For example, "Discussion rules/en", "Discussion rules/fr", "Duscussion rules/ru", etc. At the top of such page, you must put a language switch:

<languages />

and, if the language is not English, a directive to display the translated title, for example

{{DISPLAYTITLE:Règles de discussion}}

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. If there is a discrepancy between the source text and the text in the translation window, the source text is the one that needs to be translated, and the mismatch should be reported to the translation administrator.