JDOC

Page Translation Quickstart Guide/ru: Difference between revisions

From Joomla! Documentation

← Older editNewer edit →
FuzzyBot (talk | contribs)
Bots
226,300 edits
Updating to match new version of source page
FuzzyBot (talk | contribs)
Bots
226,300 edits
Updating to match new version of source page
Line 24: Line 24:
После нажатия ссылки перевода вы увидите следующий интерфейс для перевода. В документации установлен ULS (Universal Language Selector) который автоматически установит интерфейс пользователя на их локализованный язык. Это основано на браузере (его языковых настройках) и / или географическом местоположении. Настройка языка также может быть переопределена вручную, выбрав значок пользователя (вверху справа), а в раскрывающемся списке выберите язык на самом верху. Вы также можете обратиться к вашим [[Special:Preferences#mw-prefsection-personal-i18n|персональным  настройкам языка]].
После нажатия ссылки перевода вы увидите следующий интерфейс для перевода. В документации установлен ULS (Universal Language Selector) который автоматически установит интерфейс пользователя на их локализованный язык. Это основано на браузере (его языковых настройках) и / или географическом местоположении. Настройка языка также может быть переопределена вручную, выбрав значок пользователя (вверху справа), а в раскрывающемся списке выберите язык на самом верху. Вы также можете обратиться к вашим [[Special:Preferences#mw-prefsection-personal-i18n|персональным  настройкам языка]].
<div class="panel">
<div class="panel">
[[File:JDOC-translator interface-first-view-en.png]]
[[File:JDOC-translator interface-first-view-<div lang="en" dir="ltr" class="mw-content-ltr">
en
</div>.png]]
</div>
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Now you are ready to translate, click any link in the separated message units.
Now you are ready to translate, click any link in the separated message units.
</div>
<div class="panel">
<div class="panel">
[[File:JDOC-translator interface-editing-view-en.png]]
[[File:JDOC-translator interface-editing-view-<div lang="en" dir="ltr" class="mw-content-ltr">
en
</div>.png]]
</div>
</div>


You may click the suggested text to add it automatically to the edit window. Then you may edit the text. The suggested text is provided by translation services for free. There is no guarantee there will be suggested text. The suggestion query may time out at the translation services server.  
<div lang="en" dir="ltr" class="mw-content-ltr">
You may click the suggested text to add it automatically to the edit window. Then you may edit the text. The suggested text is provided by translation services for free. There is no guarantee there will be suggested text. The suggestion query may time out at the translation services server.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
When you are satisfied with your translation, save it. You can also skip sections if you only want to translate some of the message groups.
When you are satisfied with your translation, save it. You can also skip sections if you only want to translate some of the message groups.
</div>


==Page Titles==
<span lang="en" dir="ltr" class="mw-content-ltr">==Page Titles==</span>
<div lang="en" dir="ltr" class="mw-content-ltr">
Page titles '''can and should''' be translated. They are the first message group at the top of the editing interface.
Page titles '''can and should''' be translated. They are the first message group at the top of the editing interface.
{{warning|title=Important!|'''Do not translate the namespace!''' This is anything in a title proceeding and including the : (colon).}}
</div>
{{warning|title=<div lang="en" dir="ltr" class="mw-content-ltr">
Important!
</div>|<div lang="en" dir="ltr" class="mw-content-ltr">
'''Do not translate the namespace!''' This is anything in a title proceeding and including the : (colon).
</div>}}


<div lang="en" dir="ltr" class="mw-content-ltr">
A page name is in a namespace when it looks like this: "'''Prefix:'''Name of page".
A page name is in a namespace when it looks like this: "'''Prefix:'''Name of page".
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
This page name is not in a namespace when it looks like this: "Name of page".
This page name is not in a namespace when it looks like this: "Name of page".
</div>


{| class="wikitable"
{| class="wikitable"
! Correct? !! Title Examples
! <div lang="en" dir="ltr" class="mw-content-ltr">
Correct?
</div> !! <div lang="en" dir="ltr" class="mw-content-ltr">
Title Examples
</div>
|-
|-
| '''Yes!!!'''
| <div lang="en" dir="ltr" class="mw-content-ltr">
|"J2.5:Title of a Page" translated "Título de la página"
'''Yes!!!'''
</div>
|<div lang="en" dir="ltr" class="mw-content-ltr">
"J2.5:Title of a Page" translated "Título de la página"
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
"J2.5:Title of a Page" translated "Titel einer Seite"
"J2.5:Title of a Page" translated "Titel einer Seite"
</div>
|-
|-
| '''NO!'''
| <div lang="en" dir="ltr" class="mw-content-ltr">
|"J2.5:Title of a Page" translated "J2.5:Título de la página"
'''NO!'''
</div>
|<div lang="en" dir="ltr" class="mw-content-ltr">
"J2.5:Title of a Page" translated "J2.5:Título de la página"
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
"J2.5:Title of a Page" translated "J2.5:Titel einer Seite"
"J2.5:Title of a Page" translated "J2.5:Titel einer Seite"
</div>
|}
|}


Line 91: Line 127:


'''Так что помните''': Всегда добавлять Special:MyLanguage/ перед <nowiki><название исходной страницы></nowiki>. <nowiki><Название исходной страницы></nowiki> всегда непереведено. Всегда добавляйте | если он отсутствует, а затем перевод <nowiki><название исходной страницы></nowiki>.
'''Так что помните''': Всегда добавлять Special:MyLanguage/ перед <nowiki><название исходной страницы></nowiki>. <nowiki><Название исходной страницы></nowiki> всегда непереведено. Всегда добавляйте | если он отсутствует, а затем перевод <nowiki><название исходной страницы></nowiki>.
<div lang="en" dir="ltr" class="mw-content-ltr">
Often this <code><nowiki>Special:MyLanguage/</nowiki></code> is already added in the source document. So when <code><nowiki>Special:MyLanguage/JDOC:Translation Sandbox|<translate>Translation Sandbox</translate></nowiki></code> is in the original document you only have to translate <code><nowiki>Translation Sandbox</nowiki></code> and you don't see the total link.
Often this <code><nowiki>Special:MyLanguage/</nowiki></code> is already added in the source document. So when <code><nowiki>Special:MyLanguage/JDOC:Translation Sandbox|<translate>Translation Sandbox</translate></nowiki></code> is in the original document you only have to translate <code><nowiki>Translation Sandbox</nowiki></code> and you don't see the total link.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
===External Links===
===External Links===
External links are easy to translate. They are written like this in the source language.
External links are easy to translate. They are written like this in the source language.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
# <code><nowiki>http://www.php.net</nowiki></code> becomes http://www.php.net
# <code><nowiki>http://www.php.net</nowiki></code> becomes http://www.php.net
# <code><nowiki>[http://www.php.net for php information]</nowiki></code> becomes [http://www.php.net for php information]
# <code><nowiki>[http://www.php.net for php information]</nowiki></code> becomes [http://www.php.net for php information]
</div>


'''What to translate?'''  
<div lang="en" dir="ltr" class="mw-content-ltr">
'''What to translate?'''
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# This is a standard URL and will not require translating. <code><nowiki>http://www.php.net</nowiki></code> It is a regular hyperlink and must be written as such. No translation required.
# This is a standard URL and will not require translating. <code><nowiki>http://www.php.net</nowiki></code> It is a regular hyperlink and must be written as such. No translation required.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# This <code><nowiki>[http://www.php.net for php information]</nowiki></code> will only require the translation of '''for php information'''.
# This <code><nowiki>[http://www.php.net for php information]</nowiki></code> will only require the translation of '''for php information'''.
</div>


== Categories ==
<span lang="en" dir="ltr" class="mw-content-ltr">== Categories ==</span>
{{warning|title=Categories Require a Specific Method!|One thing to be aware of is that when translating a page, any 'category' links in the page should be modified to also include the appropriate language code.}}
{{warning|title=<div lang="en" dir="ltr" class="mw-content-ltr">
Categories Require a Specific Method!
</div>|<div lang="en" dir="ltr" class="mw-content-ltr">
One thing to be aware of is that when translating a page, any 'category' links in the page should be modified to also include the appropriate language code.
</div>}}


<div lang="en" dir="ltr" class="mw-content-ltr">
The translation of a category is very easy, just add '''/<language code>''' to the end of the category name.
The translation of a category is very easy, just add '''/<language code>''' to the end of the category name.
</div>


===Do This===
<span lang="en" dir="ltr" class="mw-content-ltr">===Do This===</span>
<div lang="en" dir="ltr" class="mw-content-ltr">
For example, if you translate a page from English to Spanish (language code '''es''') and the page contains the following category:
For example, if you translate a page from English to Spanish (language code '''es''') and the page contains the following category:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<pre><nowiki>[[Category:Development]]</nowiki></pre>
<pre><nowiki>[[Category:Development]]</nowiki></pre>
You need to add '''/es''' to the end of the category name.
You need to add '''/es''' to the end of the category name.
<pre><nowiki>[[Category:Developement/es]]</nowiki></pre>
<pre><nowiki>[[Category:Developement/es]]</nowiki></pre>
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Category pages can be translated as well (which should be quick - most are blank except for containing a parent category) and will be part of a special categorisation project when ready.
Category pages can be translated as well (which should be quick - most are blank except for containing a parent category) and will be part of a special categorisation project when ready.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
To be prepared for this we can add '''/nl|Ontwikkeling''' (Dutch language) at the end of the category name
To be prepared for this we can add '''/nl|Ontwikkeling''' (Dutch language) at the end of the category name
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<pre><nowiki>[[Category:Developement/nl|Ontwikkeling]]</nowiki></pre>
<pre><nowiki>[[Category:Developement/nl|Ontwikkeling]]</nowiki></pre>
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
===Do Not Do This===
===Do Not Do This===
There are a few things you should not do.
There are a few things you should not do.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
'''Please do not do this'''
'''Please do not do this'''
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Translate the word 'Category' or the name of the category.
Translate the word 'Category' or the name of the category.
<pre><nowiki>[[Category:Development]] to [[Categorie:Ontwikkeling]]</nowiki></pre>
<pre><nowiki>[[Category:Development]] to [[Categorie:Ontwikkeling]]</nowiki></pre>
</div>
{{-}}
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
'''Or this'''
'''Or this'''
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Translate just the name of the category.
Translate just the name of the category.
<pre><nowiki>[[Category:Development]] to [[Category:Ontwikkeling]]</nowiki></pre>
<pre><nowiki>[[Category:Development]] to [[Category:Ontwikkeling]]</nowiki></pre>
</div>


== Images ==
<span lang="en" dir="ltr" class="mw-content-ltr">== Images ==</span>


<div lang="en" dir="ltr" class="mw-content-ltr">
It is expected translated page will want to show images localised in the language of the page. This is encouraged because it improves the user's experience. Documentation only asks translators to follow a naming pattern of images consistent with the source language of a page.
It is expected translated page will want to show images localised in the language of the page. This is encouraged because it improves the user's experience. Documentation only asks translators to follow a naming pattern of images consistent with the source language of a page.
</div>


===Image Naming===
<span lang="en" dir="ltr" class="mw-content-ltr">===Image Naming===</span>


<div lang="en" dir="ltr" class="mw-content-ltr">
Using an image used above on this page which is written as:  
Using an image used above on this page which is written as:  
<pre><nowiki>[[File:JDOC-translator_interface-editing-view.png]]</nowiki></pre>
<pre><nowiki>[[File:JDOC-translator_interface-editing-view.png]]</nowiki></pre>
</div>


====Do This====
<span lang="en" dir="ltr" class="mw-content-ltr">====Do This====</span>


<div lang="en" dir="ltr" class="mw-content-ltr">
Keep the name of the image and just add the language code to the end:  
Keep the name of the image and just add the language code to the end:  
<pre>
<pre>
Line 149: Line 228:
português would be pt <nowiki>[[File:JDOC-translator_interface-editing-view-pt.png]]</nowiki>
português would be pt <nowiki>[[File:JDOC-translator_interface-editing-view-pt.png]]</nowiki>
</pre>
</pre>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
If the file is not a localised file type (e.g Screenshot of an interface) and is a graphic of something universal (e.g. a ball or arrow), you should not have to rename the image. If the image has a caption, you may have to translate the caption.
If the file is not a localised file type (e.g Screenshot of an interface) and is a graphic of something universal (e.g. a ball or arrow), you should not have to rename the image. If the image has a caption, you may have to translate the caption.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<pre>
<pre>
<nowiki>[[File:ball.png|caption=This is a ball]]</nowiki>
<nowiki>[[File:ball.png|caption=This is a ball]]</nowiki>
Line 156: Line 239:
<nowiki>[[File:ball.png|caption=<translate this part only>]]</nowiki>
<nowiki>[[File:ball.png|caption=<translate this part only>]]</nowiki>
</pre>
</pre>
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
After you finish translating a page with images you will localise. You should view the page in the language you just translated it too and click on the "red" file links. This will allow you to upload the localised version of the file.
After you finish translating a page with images you will localise. You should view the page in the language you just translated it too and click on the "red" file links. This will allow you to upload the localised version of the file.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Often the image in the document to translate has already a language ID which is marked for translation: <code><nowiki>[[File:JDOC-translator_interface-editing-view-<translate>en</translate>.png]]</nowiki></code>. So you will have to translate '''en''' into your local language ID (in Dutch '''nl'''). If the image has no localised items you want to translate you can translate '''en''' into '''en''' to keep the original image.
Often the image in the document to translate has already a language ID which is marked for translation: <code><nowiki>[[File:JDOC-translator_interface-editing-view-<translate>en</translate>.png]]</nowiki></code>. So you will have to translate '''en''' into your local language ID (in Dutch '''nl'''). If the image has no localised items you want to translate you can translate '''en''' into '''en''' to keep the original image.
</div>
====Не делайте этого====  
====Не делайте этого====  
If you don't insert your local image (because you don't have time at the moment) it's better not to translate '''en''' into your language, else you will have a "red" file link.  
<div lang="en" dir="ltr" class="mw-content-ltr">
If you don't insert your local image (because you don't have time at the moment) it's better not to translate '''en''' into your language, else you will have a "red" file link.
</div>


== Chunks ==  
<span lang="en" dir="ltr" class="mw-content-ltr">== Chunks ==</span>


<div lang="en" dir="ltr" class="mw-content-ltr">
Chunks are pieces of documentation which can be used at more than one place. There are big chunks, but most of them are small pieces of documentation, sometimes only one line. For example, it is used for the column headers in the helpscreens where the same fields are used in many help screens
Chunks are pieces of documentation which can be used at more than one place. There are big chunks, but most of them are small pieces of documentation, sometimes only one line. For example, it is used for the column headers in the helpscreens where the same fields are used in many help screens
</div>


===Usage of Chunks===  
<span lang="en" dir="ltr" class="mw-content-ltr">===Usage of Chunks===</span>


Using a chunk in a document is very easy. If we see: https://docs.joomla.org/Chunk30:Help_screen_column_header_Show_Title we can use it in a document with the following code:
<div lang="en" dir="ltr" class="mw-content-ltr">
<pre><nowiki>{{Chunk30:Help_screen_column_header_Show_Title/<translate>en</translate>}}</nowiki></pre>
Using a chunk in a document is very easy. If we see: https://docs.joomla.org/Chunk30:Help_screen_Show_Title we can use it in a document with the following code:
<pre><nowiki>{{Chunk30:Help_screen_Show_Title/<translate>en</translate>}}</nowiki></pre>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
If we use this in a document we see the following:
If we use this in a document we see the following:
{{Chunk30:Help_screen_column_header_Show_Title/en}}
</div>
{{Chunk30:Help_screen_Show_Title/<div lang="en" dir="ltr" class="mw-content-ltr">
en
</div>}}
<div lang="en" dir="ltr" class="mw-content-ltr">
So you will have to translate '''en''' into your local language ID (in Dutch '''nl'''). If, after translation, the chunk is not available in your language, you will see a red link. Use the link and open it in a new window. You will see a message that the document does not exist. What you must do now is:
So you will have to translate '''en''' into your local language ID (in Dutch '''nl'''). If, after translation, the chunk is not available in your language, you will see a red link. Use the link and open it in a new window. You will see a message that the document does not exist. What you must do now is:
Remove the language code in the URL, in Dutch /'''nl''', Now you will see the chunk in English. Translate the chunk into your language (only the first line is enough) and the chunk is created in your language and visible in the source document.  
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Remove the language code in the URL, in Dutch /'''nl''', Now you will see the chunk in English. Translate the chunk into your language (only the first line is enough) and the chunk is created in your language and visible in the source document.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
There is a more sophisticated way of usage of chunks, with parameters. This way you can pass parameters to the chunk in your own language. We do this with the following code:
There is a more sophisticated way of usage of chunks, with parameters. This way you can pass parameters to the chunk in your own language. We do this with the following code:
<pre><nowiki>{{Chunk30:Help_screen_toolbar_icon_Save/<translate>en</translate>|<translate>menu item</translate>}}</nowiki></pre>
<pre><nowiki>{{Chunk30:Help_screen_toolbar_icon_Save/<translate>en</translate>|<translate>menu item</translate>}}</nowiki></pre>
Line 180: Line 283:
<pre><nowiki>*'''Save'''. Saves the {{{1|item}}} and stays in the current screen.</nowiki></pre>
<pre><nowiki>*'''Save'''. Saves the {{{1|item}}} and stays in the current screen.</nowiki></pre>
When we use this in a document the result will be:
When we use this in a document the result will be:
{{Chunk30:Help_screen_toolbar_icon_Save/en|menu item}}
</div>
{{Chunk30:Help_screen_toolbar_icon_Save/<div lang="en" dir="ltr" class="mw-content-ltr">
en
</div>|<div lang="en" dir="ltr" class="mw-content-ltr">
menu item
</div>}}
<div lang="en" dir="ltr" class="mw-content-ltr">
This way the translation of '''en''' will bring us in the language we want and the translation of '''menu item''' will used in the '''item'''.
This way the translation of '''en''' will bring us in the language we want and the translation of '''menu item''' will used in the '''item'''.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
== Templates ==
== Templates ==
Templates are reusable pieces of code which have a predictable result.
Templates are reusable pieces of code which have a predictable result.
</div>


<pre>
<pre>
<div lang="en" dir="ltr" class="mw-content-ltr">
{{tip|title=This is a tip|This is the body content of a tip!}}
{{tip|title=This is a tip|This is the body content of a tip!}}
</div>
</pre>
</pre>


<div lang="en" dir="ltr" class="mw-content-ltr">
Would look like this:
Would look like this:
</div>


{{tip|title=This is a tip|This is the body content of a tip!}}
{{tip|title=<div lang="en" dir="ltr" class="mw-content-ltr">
This is a tip
</div>|<div lang="en" dir="ltr" class="mw-content-ltr">
This is the body content of a tip!
</div>}}


===Do This===
<span lang="en" dir="ltr" class="mw-content-ltr">===Do This===</span>


<div lang="en" dir="ltr" class="mw-content-ltr">
For the above example:
For the above example:
</div>
<pre>
<pre>
<div lang="en" dir="ltr" class="mw-content-ltr">
{{tip|title=This is a tip|This is the body content of a tip!}}
{{tip|title=This is a tip|This is the body content of a tip!}}
</div>
</pre>
</pre>


<div lang="en" dir="ltr" class="mw-content-ltr">
You would have to do the following:
You would have to do the following:
</div>
<pre>
<pre>
<div lang="en" dir="ltr" class="mw-content-ltr">
{{tip|title=<translate the title>|<translate the body content>}}
{{tip|title=<translate the title>|<translate the body content>}}
</div>
</pre>
</pre>


<div lang="en" dir="ltr" class="mw-content-ltr">
===Do Not Do This===
===Do Not Do This===
Here is a list of don't do's.
Here is a list of don't do's.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
*Never translate the template's name. The template {{tl|tip}} is called by the word 'tip' following the double set of curly brackets. If you translate the word tip, the translation would call a non-existent template name.
*Never translate the template's name. The template {{tl|tip}} is called by the word 'tip' following the double set of curly brackets. If you translate the word tip, the translation would call a non-existent template name.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
*Never translate the variables used in a template, only the value assigned to the variable. In the example of the {{tl|tip}} template, the word 'title' is the variable.
*Never translate the variables used in a template, only the value assigned to the variable. In the example of the {{tl|tip}} template, the word 'title' is the variable.
</div>


<noinclude>
<noinclude>
<div lang="en" dir="ltr" class="mw-content-ltr">
[[Category:Documentation Translation]]
[[Category:Documentation Translation]]
</div>
</noinclude>
</noinclude>

Revision as of 11:59, 17 March 2022

Other languages:

Эта страница должна помочь переводчику быстрее сделать первые шаги с переводами документации. Более детальная информация о переводе страниц смотрите в подробные разъяснения по переводу страниц. Чтобы зарегистрироваться в качестве переводчика, перейдите, пожалуйста, на Переводчики документации и добавьте ваше имя пользователя.

Когда ваш идентификатор пользователя будет одобрен, вы сможете найти документы для перевода на свой язык по адресу Language Statistics. Когда вы открываете документ для перевода в новом окне, вы увидите список частей для перевода. В верхней части есть ссылка на документ, который вы переводите. Откройте его в новом окне, и у вас будет все вместе. Вы можете переводить в одном окне и сравнивать с тем что вы перевели в другом.

Если вы уже записались в качестве переводчика, вы можете потренироваться в Песочнице для перевода.

Хорошо знать, как части документов отмечены для перевода. В общем, так <translate><T:number>Текст для перевода</translate> и когда вы переводите, вы увидите «Текст для перевода», который вы можете перевести. Теги <translate></translate> добавляет пользователь который отмечает документ для перевода. Тег <T:number> создается системой автоматически.

Интерфейс

Если страница готова к переводу, вы увидите (изображения ниже) или вариант (в зависимости от вида страницы):

Локализованный просмотр ссылки на английском языке

Локализованный просмотр ссылки на голландском

После нажатия ссылки перевода вы увидите следующий интерфейс для перевода. В документации установлен ULS (Universal Language Selector) который автоматически установит интерфейс пользователя на их локализованный язык. Это основано на браузере (его языковых настройках) и / или географическом местоположении. Настройка языка также может быть переопределена вручную, выбрав значок пользователя (вверху справа), а в раскрывающемся списке выберите язык на самом верху. Вы также можете обратиться к вашим персональным настройкам языка.

[[File:JDOC-translator interface-first-view-

en

.png]]

Now you are ready to translate, click any link in the separated message units.

[[File:JDOC-translator interface-editing-view-

en

.png]]

You may click the suggested text to add it automatically to the edit window. Then you may edit the text. The suggested text is provided by translation services for free. There is no guarantee there will be suggested text. The suggestion query may time out at the translation services server.

When you are satisfied with your translation, save it. You can also skip sections if you only want to translate some of the message groups.

==Page Titles==

Page titles can and should be translated. They are the first message group at the top of the editing interface.

Important!


A page name is in a namespace when it looks like this: "Prefix:Name of page".

This page name is not in a namespace when it looks like this: "Name of page".

Correct?

 !!

Title Examples

Yes!!!

"J2.5:Title of a Page" translated "Título de la página"

"J2.5:Title of a Page" translated "Titel einer Seite"

NO!

"J2.5:Title of a Page" translated "J2.5:Título de la página"

"J2.5:Title of a Page" translated "J2.5:Titel einer Seite"

Ссылки

Важная информация о ссылках

Пожалуйста, прочитайте внимательно, ссылки между страницами будут влиять на просмотр на любом языке, отличном от исходного языка. Цель состоит в том, чтобы предоставить ссылки, локализованные на языке пользователя, с которого осуществляется просмотр, и ссылки на язык пользователя, который просматривает переведенную страницу.


Информация ниже представляет собой краткий обзор. Для более подробного объяснения см.Перевод ссылок.

Стандартные ссылки на внутренние страницы

Гиперссылки на другую страницу в исходном языке являются именами страниц между [[ (brackets) ]] или варианты, как указано ниже. Хорошие стандарты для ссылок страниц должны включать правильную разметку ссылок для переведенной навигации.

  1. [[JDOC:Translation Sandbox]] becomes JDOC:Translation Sandbox
  2. [[JDOC:Translation Sandbox|Translation Sandbox]] becomes Translation Sandbox
  3. [[JDOC:Translation Sandbox|Translator Sandbox]] becomes Translator Sandbox

Ссылки с переведенной страницы на страницу на том же языке должны запускаться через процессор ссылок локализации.

  1. [[Special:MyLanguage/JDOC:Translation Sandbox]] становится Special:MyLanguage/JDOC:Translation Sandbox
    На самом деле это, не очень красивая ссылка и не отображается на языке читателя. Чтобы улучшить взаимодействие с пользователем, см. Ссылку на пример голландского перевода ниже.
  2. [[Special:MyLanguage/JDOC:Translation Sandbox|Vertaling Sandbox]] становится Vertaling Sandbox
    Теперь голландский читатель увидит ссылку на своем языке. Так же, как и выше, вы можете назвать ссылку как угодно.

Есть псевдоним к слову Special:, так что вы также можете использовать только букву S: как короткая версия Special:.

Важные советы по ссылкам

  • Всегда используйте 
    [[Special:MyLanguage/<исходный язык>|<перевод>]]
  • Или 
    [[S:MyLanguage/<исходный язык>|<перевод>]]

Как пример может быть: 

[[JDOC:Translation Sandbox|Translation Sandbox]] 
  is translated as
[[Special:MyLanguage/JDOC:Translation Sandbox|Vertaling Sandbox]]
 or
[[S:MyLanguage/JDOC:Translation Sandbox|Vertaling Sandbox]]

Так что помните: Всегда добавлять Special:MyLanguage/ перед <название исходной страницы>. <Название исходной страницы> всегда непереведено. Всегда добавляйте | если он отсутствует, а затем перевод <название исходной страницы>.

Often this Special:MyLanguage/ is already added in the source document. So when Special:MyLanguage/JDOC:Translation Sandbox|<translate>Translation Sandbox</translate> is in the original document you only have to translate Translation Sandbox and you don't see the total link.

External Links

External links are easy to translate. They are written like this in the source language.

  1. http://www.php.net becomes http://www.php.net
  2. [http://www.php.net for php information] becomes for php information

What to translate?

  1. This is a standard URL and will not require translating. http://www.php.net It is a regular hyperlink and must be written as such. No translation required.
  1. This [http://www.php.net for php information] will only require the translation of for php information.

== Categories ==

Categories Require a Specific Method!


The translation of a category is very easy, just add /<language code> to the end of the category name.

===Do This===

For example, if you translate a page from English to Spanish (language code es) and the page contains the following category: 

[[Category:Development]]

You need to add /es to the end of the category name. 

[[Category:Developement/es]]

Category pages can be translated as well (which should be quick - most are blank except for containing a parent category) and will be part of a special categorisation project when ready.

To be prepared for this we can add /nl|Ontwikkeling (Dutch language) at the end of the category name 

[[Category:Developement/nl|Ontwikkeling]]

Do Not Do This

There are a few things you should not do.

Please do not do this

Translate the word 'Category' or the name of the category. 

[[Category:Development]] to [[Categorie:Ontwikkeling]]

Or this

Translate just the name of the category. 

[[Category:Development]] to [[Category:Ontwikkeling]]

== Images ==

It is expected translated page will want to show images localised in the language of the page. This is encouraged because it improves the user's experience. Documentation only asks translators to follow a naming pattern of images consistent with the source language of a page.

===Image Naming===

Using an image used above on this page which is written as: 

[[File:JDOC-translator_interface-editing-view.png]]

====Do This====

Keep the name of the image and just add the language code to the end: 

español would be es [[File:JDOC-translator_interface-editing-view-es.png]]
italiano would be it [[File:JDOC-translator_interface-editing-view-it.png]]
português would be pt [[File:JDOC-translator_interface-editing-view-pt.png]]

If the file is not a localised file type (e.g Screenshot of an interface) and is a graphic of something universal (e.g. a ball or arrow), you should not have to rename the image. If the image has a caption, you may have to translate the caption. 

[[File:ball.png|caption=This is a ball]]
Will become
[[File:ball.png|caption=<translate this part only>]]

After you finish translating a page with images you will localise. You should view the page in the language you just translated it too and click on the "red" file links. This will allow you to upload the localised version of the file.

Often the image in the document to translate has already a language ID which is marked for translation: [[File:JDOC-translator_interface-editing-view-<translate>en</translate>.png]]. So you will have to translate en into your local language ID (in Dutch nl). If the image has no localised items you want to translate you can translate en into en to keep the original image.

Не делайте этого

If you don't insert your local image (because you don't have time at the moment) it's better not to translate en into your language, else you will have a "red" file link.

== Chunks ==

Chunks are pieces of documentation which can be used at more than one place. There are big chunks, but most of them are small pieces of documentation, sometimes only one line. For example, it is used for the column headers in the helpscreens where the same fields are used in many help screens

===Usage of Chunks===

Using a chunk in a document is very easy. If we see: https://docs.joomla.org/Chunk30:Help_screen_Show_Title we can use it in a document with the following code: 

{{Chunk30:Help_screen_Show_Title/<translate>en</translate>}}

If we use this in a document we see the following:

{{Chunk30:Help_screen_Show_Title/

en

}}

So you will have to translate en into your local language ID (in Dutch nl). If, after translation, the chunk is not available in your language, you will see a red link. Use the link and open it in a new window. You will see a message that the document does not exist. What you must do now is:

Remove the language code in the URL, in Dutch /nl, Now you will see the chunk in English. Translate the chunk into your language (only the first line is enough) and the chunk is created in your language and visible in the source document.

There is a more sophisticated way of usage of chunks, with parameters. This way you can pass parameters to the chunk in your own language. We do this with the following code: 

{{Chunk30:Help_screen_toolbar_icon_Save/<translate>en</translate>|<translate>menu item</translate>}}

The source of this chunk is: 

*'''Save'''. Saves the {{{1|item}}} and stays in the current screen.

When we use this in a document the result will be:

{{Chunk30:Help_screen_toolbar_icon_Save/

en

|

menu item

}}

This way the translation of en will bring us in the language we want and the translation of menu item will used in the item.

Templates

Templates are reusable pieces of code which have a predictable result. 

<div lang="en" dir="ltr" class="mw-content-ltr">
{{tip|title=This is a tip|This is the body content of a tip!}}
</div>

Would look like this:

This is a tip

===Do This===

For the above example: 

<div lang="en" dir="ltr" class="mw-content-ltr">
{{tip|title=This is a tip|This is the body content of a tip!}}
</div>

You would have to do the following: 

<div lang="en" dir="ltr" class="mw-content-ltr">
{{tip|title=<translate the title>|<translate the body content>}}
</div>

Do Not Do This

Here is a list of don't do's.

  • Never translate the template's name. The template {{tip}} is called by the word 'tip' following the double set of curly brackets. If you translate the word tip, the translation would call a non-existent template name.
  • Never translate the variables used in a template, only the value assigned to the variable. In the example of the {{tip}} template, the word 'title' is the variable.


Retrieved from "https://docs.sandbox.joomla.org/index.php?title=JDOC:Page_Translation_Quickstart_Guide/ru&oldid=893349"