Help:विस्तारक:भाषांतर करा

This page is a translated version of the page Help:Extension:Translate and the translation is 52% complete.

Outdated translations are marked like this.

भाषांतरकार (main help page )

भाषांतर प्रशासक

प्रणाली-प्रशासक व विकसक

भाषांतर विस्तारक हे भाषांतर करण्यास आवश्यक ते फिचर्स जोडून मिडियाविकिला सुशोभित करते. त्याचा आशय पानांच्या भाषांतरास, विकिचे आंतरपृष्ठ, व इतर संचेतन उत्पादनांसह, जसे, translatewiki.net वरही वापर करण्यात येतो. The Translate extension comes with an easy to use translation interface and can separate the content structure from the text content that needs to be translated, showing only the translatable text to translators by splitting the content into manageable units. Each unit is automatically tracked for changes, and translators immediately see what needs updating on a specific page or throughout the wiki.

अनेक भाषांतरकारातर्फे, भाषांतर विस्तारकाचा,मिडियाविकिचे सदस्य आंतरपृष्ठ व इतर संचेतन प्रकल्पांमध्ये भाषांतर करण्यास प्रत्येक महिन्यात वापर करण्यात येतो. userbase.kde.org वर त्याचा वापर, जवळपास एक हजार पानांच्या सदस्य दस्ताऐवजीकरणाचे भाषांतर करण्यासाठी करण्यात येतो. भाषांतर विस्तारक हे वापर सुरु करण्यास फार सोपे आहे, पण त्याच वेळी ते प्रगत अहवालाचे मापन, पुनरावलोकन व कार्यप्रवाह प्रारुपण पण करते व ते पुरविते.

फिचर्स

भाषांतर संपादक:एक संदेश,उपयुक्त सूचनेसह(चित्रात दर्शविले नाही)व दोन सहाय्यक भाषांत सुचवण्या

आंतरपृष्ठ: भाषांतर विस्तारकाचे मुख्य प्रारुप हे एक सोपी तरी कार्यकारी भाषांतर आंतरपृष्ठ आहे. संदेश व्याख्या व दस्ताऐवजीकरण अश्या आवश्यक माहितीसमवेतच, आपण इतर भाषांतील भाषंतरेही बघु शकता. जर व्याख्या बदलली तर,आपण ते बदल पाहू शकता. हे विस्तारक,एकीकडेच दिलेले कंसचिन्ह व न-वापरलेली चले अश्यासारख्या काही सामान्य चूकांमध्ये मदत करण्यास, काही अंतर्बांधित तपासण्यासह येते. Depending on the configuration, there are also suggestions from translation memory and machine translation services like those of Google Translate, Microsoft's Bing Translator and Apertium.

The usability of the translation interface is enhanced with JavaScript and AJAX. The backend provides WebAPIs that can be used in mobile interfaces or interfaces tailored to specific kind of content. It is also possible to export messages for translation in other off-line and on-line tools that accept the Gettext po file format.

संदेश गट व नेमलेली कार्ये:अत्याधिक प्रारुपे ही या दोनच मूळ संकल्पनेभोवती गुंफलेली असतात:संदेश गट व नेमलेली कार्ये.

संदेश गट हा संदेश संकलनाचे प्रतिनिधित्व करतो. एका आशय पानाचा एक गट असतो,ज्यात, प्रत्येक परिच्छेद हा त्या गटातील, सोप्या आकारातील एक संदेश असतो. प्रत्येक मिडियाविकि विस्तारकात वापरल्या जाणारे संदेश हेtranslatewiki.net वर एक गट बनवितात- त्यापैकी काही महत्तम विस्तारकांना बहुविध गट असतात.आपण एखाद्या गटांचा एक गट बनवु शकता, जसे, "सर्व बातमीपत्रे" किंवा "सर्व भाषांतर विस्तारक संदेश". अत्याधिक सांख्यिकी व नेमलेली कार्ये ही संदेश गट पातळीवरच काम करतात.

The tasks, or in other words different listings of messages in a message group, facilitate different use cases. Normally a translator gets a list of all untranslated messages in a chosen message group, but there are tasks where you can review messages or just get a list of all messages, translated or not.

हे विशेष पान प्रत्येक संदेश गटांची भाषांतराच्या स्थितीचा अहवाल देते.

Reporting and statistics: The extension has extensive reporting features ranging from a view of untranslated messages across all message groups in a given language to lists of translators per language with their activity level.

Content translation: If you have ever tried to translate content in MediaWiki without any tools, you know it does not scale. The translated versions get out of date and there is no way to track changes to the master page, so there are many half-translated and outdated translations without a clear overview of the overall status. Translators often feel discouraged when they cannot work with small manageable pieces of text. Translators don't find what to work on or what needs updating. The users also get confused by outdated information.

This is all solved with the Translate extension and its page translation feature. It adds a bit of overhead to the pages that need translation, but the benefits far outweigh this. Essentially you only need to mark the parts of the page that need translation. The extension then splits such parts into paragraph sized units and creates a message group for them. After that translators can use all the features described above. In addition you can easily add a language bar with the ‎<languages /> tag or have links automatically go to the user's preferred language version (only) when it exists, by using links of the form [[Special:MyLanguage/Pagename]].

For more information see the tutorial How to set up a content page for translation and the in-depth documentation of the page translation feature.

Developers: The extension comes with built-in support for many common translation file formats, like Java properties and Gettext po files. It has an extensive set of tools, both in-wiki and on the command line, to efficiently import and export translations.

Searching: Without a search feature, it is difficult for translators to find specific messages they want to translate. Traversing all the translations or strings of the project is inefficient. Also, translators often want to check how a specific term was translated in a certain language across the project.

This is solved by the special page Special:SearchTranslations. Translators can find the messages containing certain terms in any language and filter by various criteria: this is the default. After searching, they can switch the results to the translations of said messages, for instance to find the existing, missing or outdated translations of a certain term.

Use cases

You can translate almost anything with the Translate extension. Naturally there are specialized tools for translation of certain kind of content like video subtitles, that are better done with those tools, but in general Translate performs very well with any kind of text that can be split into messages with length ranging from one word up to one large paragraph. Longer messages become unwieldy to translate and are just harder to work with.

The three primary use cases that the Translate extension supports are content translation, local interface translation and software translation. All of them are covered in the following sections, with links to tutorials and to reference documentation or in-depth topical help where available. Of the three use cases the interface translation has been utilized the least.

आशय भाषांतर

हे भाषांतर कालबाह्य आहे: कालबाह्य भाग हे नविन स्रोत मजकूराने बदलविल्या जातात व भाषांतरकार हे, त्या अद्यतन करावयाच्या संदेशापर्यंत एकाच टिचकीत पोहोचू शकतात.

Most wikis have content they would like to be available in multiple languages. Whether just a few or hundreds of pages, it doesn't matter. In order to prevent wasting translator's time, pages should be marked for translation only when they are reasonably stable. Each change that is made afterwards can affect tens or hundreds of old translations, and the time needed to update them adds up. Especially with volunteer translators, you should be aware of this aspect, and respect the time they spend making translations and updates, avoiding unnecessary work. If you use the Translate extension to translate pages, you are already well on your way to using the translator time available in the most effective and efficient way.

The way the Translate extension splits up a page into paragraph sized units does not leave too much freedom for translators to change the content. This is usually a good thing and is ideal where continuity and consistency of content across languages is desired. It can be worked around, but in principle this way of doing translations is not generally suitable, for example, for Wikipedia articles, which usually are totally independent of each other. Even if they originally start as a translation from a different language, they usually begin living their own independent life from the original version. With Translate, the original page is always the main version, and new content cannot be developed in translated versions.

With these limitations in mind there are still plenty of cases where this feature is a perfect match. Most, if not all, user documentation falls into this category as well as news-like content that does not change once written. If you have the Translate extension already installed and access rights configured, try creating a page and wrapping the whole text inside <languages /><translate>...</translate> and follow the links, or follow the tutorial How to prepare a page for translation.

Groups of pages can be further aggregated together with the Special:AggregateGroups page.

बहुभाषिक विकित स्थानिक आंतरपृष्ठाचे भाषांतर

One thing almost every wiki has customized is the sidebar. It is possible to create a message group for the custom sidebar messages and also for other local interface customisations.

One interesting expansion is the multilingual pages or templates built with the {{int:}} magic word. The translatewiki.net main page and some Wikimedia Commons templates are good examples of this. The magic word {{int:}} is an alternative to the content translation feature and it is more suitable to mark-up heavy pages just like the translatewiki.net main page. Another nice feature is that the language of the page automatically follows the user interface language, so there is no need for a language bar, although you might want to have an interface language selector instead.

Setting this up is currently a bit more complicated than content translation and needs software configuration, but it is all covered in the tutorial How to make an interface message group.

संचेतनाचे भाषांतर

The Translate extension is a good fit for translating software interface messages. At translatewiki.net, it is used to translate dozens of software products from games to web applications. The Translate extension supports reading and updating translations from and to common formats used in web development including Java properties, Gettext and Yaml files.

Change tracking is also available for externally tracked files, because internally the extension uses a cached derivative version of the localisation files where the source text and its translations are stored, instead of using them directly in their original format. Translation administrators can either use the web interface or a command line interface to check new message definitions and "fuzzy" (request update of) translations when they need updating. This works regardless of the underlying file format or version control system (if any).

With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your VCS repository checkout, where you can easily commit changes and new files.

पुढील वाचन व वर्गपाठ

Help:विस्तारक:भाषांतर करा

Contents

फिचर्स

Use cases

आशय भाषांतर

बहुभाषिक विकित स्थानिक आंतरपृष्ठाचे भाषांतर

संचेतनाचे भाषांतर

पुढील वाचन व वर्गपाठ

भाषांतरकार व भाषांतर प्रशासकांसाठी

भाषांतर प्रशासकांसाठी

विकसकांसाठी संदर्भ दस्तऐवज

संबंधित