Help:Extension:Translate/Page translation example/hi

स्वागत है! इस ट्यूटोरियल को पूरा करने के बाद आप अनुवाद एक्सटेंशन की मदद से अनुवाद-योग्य पृष्ठ बनाना और प्रबंधित करना सीख जाएँगे। हम इस ट्यूटोरियल को जितना हो सके उतना छोटा रखने की कोशिश करेंगे और साथ में सारी बुनियादी परिकल्पनाओं और कार्यों को भी परिचित कराएँगे। इस ट्यूटोरियल को पूरा करने के बाद आप पृष्ठ अनुवाद सुविधा के बारे में विस्तृत प्रलेखन को पढ़ पाएँगे।

कुछ वीडियो ट्यूटोरियल भी हैं जो इस अनुभाग को दर्शाते हैं, और आप इनकी मदद से भी अनुवाद एक्सटेंशन को चलाना सीख सकते हैं:

चरण 1: प्रारंभ करने से पहले
== यह ट्यूटोरियल मानता है कि अनुवाद एक्सटेंशन पहले से इंस्टॉल और कॉन्फ़िगर किया गया है। हो सकता है कि आपके पास पहले से ही एक ऐसा पृष्ठ हो जिसे अनुवाद की आवश्यकता हो, या आप नीचे दिए गए उदाहरण पृष्ठ का उपयोग इस ट्यूटोरियल  अपनी खुद की विकि  में दिए गए चरणों को आज़माने के लिए कर सकते हैं। Maybe you already have a page in mind that needs translation, or you can use the example page provided below to try out the steps in this tutorial in your own wiki.

यह एक पृष्ठ है जो फ्रेटिंगा की काल्पनिक नगरपालिका का वर्णन करता है।

Here is the wikicode associated to it :

Fréttinga is a small municipality in MungoLand, located on the BaMungo island. It hosts a population of about 400 people. It has some agriculture and fishing. Tourists like to visit it in the summertime. == Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day.


 * 1. Go to the page  in your wiki (or a draft page) and click create.
 * 2. Paste the above content and save it.

चरण 2: तैयारी
अब हमारे पास कुछ पाठ के साथ एक पृष्ठ है। यदि पृष्ठ अभी भी बहुत सारे परिवर्तनों के अधीन होने वाला है, तो अनुवाद प्रणाली में पृष्ठ को जोड़ने से पहले संपादन को सामान्य स्तर तक धीमा करने तक इंतजार करना बेहतर होगा। यह अनुवादकों के लिए बहुत अधिक काम से बचने के लिए है क्योंकि उन्हें सभी परिवर्तनों के साथ रखने की आवश्यकता है

If the page is still going to be subject to lots of changes, it may be better to wait until the edits slow down to a normal level before adding the page into the translation system. This is to avoid too much work for translators as they need to keep up with all the changes.

The page is ready for translation ? So let's see how to request translation :


 * 3. Edit
 * 4. Wrap the whole content inside  tags as shown below
 * 5. Save the page

 Fréttinga is a small municipality in MungoLand, located on the BaMungo island. It hosts a population of about 400 people. It has some agriculture and fishing. Tourists like to visit it in the summertime. == Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day. 

You don't need to add tags to all elements.

You should never add markers like yourself; the extension does it for you in the next step.

चरण 3: अनुवाद सक्षम करना
पृष्ठ को सहेजने के बाद, आप पृष्ठ के शीर्ष पर एक लिंक देखेंगे "" अनुवाद के लिए इस पृष्ठ को चिह्नित करें "या" इस पृष्ठ में अनुवाद शामिल किए गए बदलावों को शामिल किया गया है। "यदि आप अनुवाद अनुवाद प्रशंसक नहीं हैं, तो आप एक अनुवाद प्रशासक हैं, तो" अनुवाद के लिए इस पृष्ठ को चिह्नित करें "लिंक पर क्लिक करें। पृष्ठ को स्वचालित रूप से चार अनुवाद इकाइयों में विभाजित किया गया है। पहली इकाई पृष्ठ का शीर्षक है, दूसरा पैराग्राफ है, दूसरा तीसरा है पैराग्राफ का दूसरा पैराग्राफ है, और चौथा दूसरा पैराग्राफ का पाठ है। यह अनुवाद है, जो कि अनुवादक के विभिन्न मूल्यों हैं: प्रत्येक इकाई स्वतंत्र है; यह पृष्ठ के रूप में अनुवादित किया जा सकता है; पृष्ठ सामग्री में परिवर्तन इकाई स्तर में ट्रैक किए जाते हैं। इकाइयों को पुनर्गठन किया जा सकता है या हटाया जा सकता है। If you are a translation administrator, then click on the "Mark this page for translation" link.  The page has been automatically split into four translation units. The first unit is the title of the page, the second is the first paragraph, the third is the header of the second paragraph, and the fourth is the text of the second paragraph. These are the basics items of translatable pages: each unit is independent; it can and must be translated as a whole; changes to the page content are tracked into the unit level. Units can be rearranged or deleted.

There is also a view of the page translation page template; this will be covered in later steps. You can give names to the translation units, but in this example, we choose to stick with the defaults.


 * 6. Click the "Mark this page for translation" link
 * 7. Ensure that the page body is split into three units correctly
 * 8. Click the "Mark this version for translation" button (reminder: you have to be a Translation administrator for this)
 * 9. Return to the page

Now you will see a new link at the top, "Translate this page", that lets translators translate the page. You might have a look at the translation tutorial which uses this page as an example and try out few translations now. Then return here for the next step.

Understanding how changes are impacting translations and translations units
Tracking changes is a very important feature, so let's make some changes and see how it works. When you open the page for editing you will see that it has been modified with markers like. These are added by the extension and help it identify which unit is which. This allows you to rearrange and edit those units. When editing the page, the markers should be left alone and their position in relation to the unit they belong to should not be changed. When moving a unit, move the unit marker, too.

When deleting a unit, delete the marker too. When adding new paragraphs, new markers will be added by the software. Do not try to do this manually, it may confuse the software. Markers you have deleted will also be automatically deleted by the bot in the existing translations.

If you do minor changes to an existing translation unit (adding a few words or a link to a paragraph), keep the marker. If you change a whole paragraph (delete and rebuilt it), delete the marker. This way, translators will have different tasks, between reviewing a fuzzy translation or create a new translation.

let's modify something !
Here is what you will do :


 * 10. Make some additions as highlighted above
 * 11. Click the "marked for translation" link at the top
 * 12. Observe the changes
 * 13. Click the "Mark for translation" button (reminder: you have to be a Translation administrator for this)
 * 14. Return to the original page

If you made translations as suggested in the previous step, you can now see those translations linked at the top of the page. You will also see that the translation is not 100 % up to date. If you go to the translation view, you see that the unit is marked as in need of updating.

पुरानी अनुवाद अंग्रेजी पाठ द्वारा प्रतिस्थापित किया जाता है; उपयोगकर्ता को बताया जाता है कि अनुवाद अधूरा है

The translation template view helps you to see what parts of the page are constant in all language versions (the "translation page template", i.e. the parts outside translate tags) and also shows you if units have been moved around or deleted.

सभी अनुवादित संस्करणों को अपडेट करने से पहले थोड़ी देरी हो सकती है, क्योंकि अपडेट करने के लिए कई पृष्ठ हो सकते हैं।

अब आप मूल बातें जानते हैं, लेकिन यह ट्यूटोरियल उन अधिक चीजों के साथ जारी रहेगा जो आपके मुठभेड़ की संभावना है।

Adding an image, a category and a list with translation markers
You have a basic translatable page now, but it is very dull. Let's add an image and some other stuff to make it look more like a normal wiki page and see how those elements interact with translation.

हमने इसके इकाई मार्कर सहित एक पैराग्राफ भी हटा दिया, और इसे एक सूची के साथ बदल दिया, ताकि आप देख सकें कि क्या होता है।


 * 15. Add an image, a category and a list to the page as shown below
 * 16. Save the page
 * 17. Click the link "marked for translation" at the top of the page
 * 18. Verify that the changes look as intended
 * 19. Click the "Mark this version for translation" button
 * 20. Return to the translatable page

पृष्ठ अनुवाद
Allowing to translate only the picture title:

Or allowing to change the image file in the translated page (for localized version for exemple) and the title:

यहां आप देख सकते हैं कि हमने अनुवाद इकाई के बाहर अधिकांश छवि मार्कअप छोड़ दिया है और इसके बजाय अनुवाद पृष्ठ टेम्पलेट में है। यह आमतौर पर ठीक है, लेकिन कभी-कभी अनुवादक छवि को बदलना चाहते हैं, खासकर अगर इसमें भाषाई सामग्री (पाठ) हो।  उन मामलों में आमतौर पर एक यूनिट में पूरे मार्कअप को शामिल करना आसान होता है (जैसा कि हमने श्रेणी के लिए किया था)।  जब एक इकाई के अनुवाद में मार्कअप शामिल होता है या उसके साथ बातचीत होती है, तो अनुवादकों को इसके बारे में एक छोटी सी टिप लिखना एक अच्छा विचार है।  आप इसे निम्न चरणों के साथ कर सकते हैं। (reminder: the translation page template doesn't change between the different translated pages) This is usually okay, but sometimes translators may want to change the image, especially if it contains linguistic content (text). In those cases it's usually easiest to include the whole markup in a unit (as we did for the category).

When the translation of a unit involves or interacts with markup it's a good idea to write a small tip to the translators about it. You can do this with the following steps.


 * 21. Click "Translate this page" link at the top
 * 22. Select "qqq - Page documentation" language
 * 23. Click the message name which contains the message "A typical view of Fréttinga"
 * 24. Write "Description of an image" and click "Save"

Now, the documentation "Description of an image" is shown next to the to-be-translated-title of the image.

लिंक के बारे में
Similarly, for links there are many ways to do it. We used, which automatically redirects to the translated version of the page depending on the users' interface language (if that translation exists). This isn't an ultimate solution, because users will always be redirected to the interface language they are using, not to the language they are currently reading. Special:MyLanguage also interferes with Special:WhatLinksHere and makes it not work. The good thing about Special:MyLanguage is that you always get some version of the page, even if the requested translation doesn't exist.

श्रेणियों के बारे में
In this example, the whole category assignment is a translation unit. This lets translators change it to or whatever naming convention you want to use for categories. If it were outside the translation template, you would have all the pages Foo, Foo/de, Foo/ru, Foo/ta and so on in the same category. Sometimes this is okay, but usually it distracts the users. Make sure your translators know what the local convention is.

शीर्षकों के बारे में
शीर्षक को पाठ से अलग तत्वों के रूप में माना जाता है, शीर्षक और पैराग्राफ के बीच एक  रिक्त  लाइन (अगर वहाँ पहले से ही नहीं है) जोड़ना न भूलें।

निम्नलिखित उदाहरण केवल एक अनुवाद इकाई बनाएगा:

== Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day.

अगले एक शीर्षक के लिए एक सहित दो अनुवाद इकाइयों, पैदा करेगा।

== Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day.

Adding a blank line allows translators to know when they can take a break. Plus it prevents issues with wikitext.

Operating on the whole page and its translations
It is also possible to move translatable pages including all their translations to a new name. Because many pages may need to be moved, this operation is not instant. You can delete either the whole page including all translations, or just one translated version of a page. You can access these functions from the same place they are on all other pages.

Managing all wiki's pages translations with Special pages
Special:PageTranslation lists all the pages in the system. Besides giving you an overview of all translatable pages, it is also possible to discourage pages from translation. This hides the page from most lists. It does not prevent further translations.

Now, you know !
You have now created a translatable page and tried all of the common actions that can be performed on translatable pages.

Going deeper ?
For more information, or if you want to understand the feature more deeply, please continue reading on the in-depth documentation of page translation feature. It also contains discussion about different ways of handling links, categories and templates, or pros and cons of using larger or smaller translation units.