Online Manual:Translation Portal: Difference between revisions From Online Manual

Jump to: navigation, search
Line 81: Line 81:


==Tips and trick about translations==
==Tips and trick about translations==
===Headlines, templates and line spacing===
===Headlines, templates, other formatting and line spacing===
Just noticed:
Just noticed:
{{code|1=<nowiki>{{Other languages}}
{{code|1=<nowiki>{{Other languages}}
Line 94: Line 94:
<translate><!--T:1-->
<translate><!--T:1-->
===View All Members===</nowiki>}}
===View All Members===</nowiki>}}
The same applies to any kind of text: always leave a white line between the templates at the beginning of the page and the translate tag.
===Redirects===
Once a page is marked for translation is impossible to "revoke" this mark and let the page behave like a normal one. The same applies to redirects too.<br>
But redirects are more complicated: for example if the content of a page (let's say page_A) is moved to another page (page_B for this example), page_A is redirected to page_B and page_B is marked for translation, the translate extension will show the entries twice. Additionally if a placeholder is used in the redirect (e.g. <nowiki>&nbsp;</nowiki> in page_A) and is marked for translation, for sure if the id of the translation unit is the same as one of the ids in page_B there will be problems in particular while translating the unit with the same name.
The workaround used temporarily is to avoid the redirect and use a message in the page that should contain the redirect with a link to the new page and being sure that there are no conflicts between .
'''Alternative solution to be tested'''<br>
Use a placeholder in the redirect page and name the translation unit something totally different from any other unit in the proper page.

Revision as of 19:36, 4 August 2011

This is a project page for Translators. Translators can check in here to find out what they can do. If you have any questions about this information, or suggestions for improving this page, please discuss at Online Manual talk:Translation Portal

Pages Ready for Translation

These pages appear in the new help tab, and are ready for translation. As soon as you save a translation message (like a language string), it will immediately be available to all users of the wiki and the new help tab.

  • Registering - Many forums require users to register to gain full access.
  • Posting - The whole point of a forum, posting allows users to express themselves.
  • Search - Searching is an extremely helpful tool for finding information in posts and topics.
  • Logging In - After registering you need to login to really gain full access to the forum.
  • Bulletin Board Code - Posts can be spiced up with a little BBC.
  • Memberlist - The memberlist shows all the members of a forum.
  • Features- Here is a list of the most popular features in SMF.
  • Profile - Each member has their own personal profile.
  • Calendar - Users can keep track of events, holidays, and birthdays with the calendar.
  • Personal messages - Users can send personal messages to each other.

How to translate these pages

These translations will be done using a wiki extension called the Translate extension, provided by the translatewiki team. To begin, go to the base page to be translated. If you have permission to translate, you will see a link titled "Translate this page" before the content of the page. Follow the link to the Translate form. You'll see the page's name listed in "Group". Choose the language from the drop-down list, and hit the "Fetch" button.

You will see all the language strings which need to be translated. The translation tool calls them messages. The link for the language message is on the left, and the content is on the right. Click on the link to start an editing window for that message. Above the editing window, you will see the source text, labeled "Message definition". In the textarea below, you may begin typing in the translation. If you wish, enter a Summary to discribe the changes you have made. When you have completed translating the language message, you must use the "Save page" button to save the language message you are editing on this page.

For more information on translating, please see the Page translation feature documentation from the translatewiki team

Note about links translation - Unfortunately at the moment the only way to have translations not marked as outdated by the extension is to use the english form of the link (i.e. without any language code like en, it, fr, etc. at the end). A "special case" that should be handled by the extension, but apparently is not, are intra-page anchors (e.g. [[#Pages Ready for Translation]]) in that cases the anchor must be translated, but the extension will outline the sentence containing it as outdated (see this page to have an idea of the result). For the time being let's live with it, eventually we will find the cause and fix it.

How to translate a template

In wikimedia a template is a special page that can be used within other pages to repeat consistently informations and/or structures (e.g. boxes like Template:Version specific). Templates can contain HTML, formatting entities, logical constructs and of course text. HTML, formatting and logical operators must not be translated, while text should be.

The translation of a template follows a different approach then the translation of a normal page.

Haven't these translations already been done for the old help tab

The old Help tab and the current text found here on the wiki came from the same source -- the old online documentation at http://docs.simplemachines.org/. So the new help files are very similar to the old help tab documentation. In some places, the information has been updated. This means you may be able to find translations in the old help tab or in the language files (or in the Language Editor, if you are an SMF LE translator). If the new wiki language message is still a good match to the old help tab string, you can copy and paste the the old translation into the wiki.

Hey! What happened to the wiki translation I did earlier

To those of you who tried out translation before we finished setting things up -- thank you. It helped us see how things were going to work. We apologize for all the confusing changes. Now that the wiki has moved out of beta, we will avoid making so many confusing changes in the future.

If you did some earlier translation on the wiki, and it no longer shows up, you can find it in the history. So if you worked on translating part of Registering/nl but don't see it now -- click the history button to find your older version of a page. If your earlier work in one browser window, and use the wiki translation tool in another browser window, you will be able to cut-and-paste your work into the appropriate language message. You can cut and paste your translations into the appropriate language http://wiki.simplemachines.org/smf/index.php?title=Registering/nl&action=history. As long as it is still a good match for the one of the current language "messages", you can just copy and paste it into the correct message. Thanks for your help and your patience.

Pages with older translations

Pages not yet ready for translation

These pages already appear in the help tab. Each one requires some work. As each file becomes "stable", it will be released for translation.

Some things site admins would like to do to make translation easier and better

We are in the early stages of translating pages on the wiki, so we are still learning about the best way to get everything set up, and about any problems that might arise. Please let us know if you run into difficulties, or need more information.

Here is our plan to get the wiki ready for translation:

  1. Make sure the translate extension is in place and working well. (good to go!)
  2. Make sure the pages are all in a final version and a "translator friendly" state (Some pages are ready now!)
  3. Add information the translators need
    • How to find pages that need translation (Special:PageTranslation)
    • Create our own local guide to translation, so we don't have to depend on the translatewiki.net teams documentation

Tips and trick about translations

Headlines, templates, other formatting and line spacing

Just noticed: 

{{Other languages}}
{{TOCright}}
<translate><!--T:1-->
===View All Members===

will result in the headline no being properly displayed in translated pages (i.e. the triple equals doesn't get translated to a heading and remains as it is). To solve the issue, please use an empty line between the last template and the translate tag: 

{{Other languages}}
{{TOCright}}

<translate><!--T:1-->
===View All Members===

The same applies to any kind of text: always leave a white line between the templates at the beginning of the page and the translate tag.

Redirects

Once a page is marked for translation is impossible to "revoke" this mark and let the page behave like a normal one. The same applies to redirects too.
But redirects are more complicated: for example if the content of a page (let's say page_A) is moved to another page (page_B for this example), page_A is redirected to page_B and page_B is marked for translation, the translate extension will show the entries twice. Additionally if a placeholder is used in the redirect (e.g.   in page_A) and is marked for translation, for sure if the id of the translation unit is the same as one of the ids in page_B there will be problems in particular while translating the unit with the same name.

The workaround used temporarily is to avoid the redirect and use a message in the page that should contain the redirect with a link to the new page and being sure that there are no conflicts between .

Alternative solution to be tested
Use a placeholder in the redirect page and name the translation unit something totally different from any other unit in the proper page.

Retrieved from "https://wiki.simplemachines.org/w/index.php?title=Online_Manual:Translation_Portal&oldid=8679"


Advertisement: