Compare Revisions

Translating an article

Revision 87773:

Revision 87773 by vesper on

Revision 93778:

Revision 93778 by vesper on

Keywords:

Search results summary:

Learn how to translate a full SUMO article from start to finish. Includes useful tips and important information.
Learn how to translate a full SUMO article from start to finish. Includes useful tips and important information.

Content:

==Who do I talk to if I have questions?== At some point we were all new to localizing in SUMO, so having questions is welcome and encouraged. The more you ask, the more you know! To get answers, you should find the right people to talk to. You can find us at the following places: * [https://client00.chat.mibbit.com/?server=irc.mozilla.org&channel=%23sumo-1l0ns #/sumo-l10ns channel] on IRC * [https://client00.chat.mibbit.com/?server=irc.mozilla.org&channel=%23sumo #sumo channel] on IRC * [https://support.mozilla.org/forums/l10n-forum/ SUMO l10n forum] on this site You should also stay in touch with your Locale Leaders. You can find them by [https://support.mozilla.org/kb/locales going to the locale list] and clicking your language in the list. Your Locale Leaders are the best people to ask for advice and most up-to-date information regarding the localization of SUMO into your language. === Translating an article === {note}'''IMPORTANT:''' The information below is universal to all locales. To get detailed information about localizing into your language, please get in touch with your Locale Leaders - they will tell you what style of language to use and what to look out for. Thank you!{/note} * Go to [/localization your localization dashboard]. <!-- SCREENSHOT GOES HERE --> * At the very top there is a list of the most visited articles. Pick and click the first article you see marked with a red triangle, expand {menu Editing Tools} on the left, and then click {menu Translate Article}. <!-- SCREENSHOT GOES HERE --> * On the next page the English version is displayed on the left hand side, the translation goes into the right hand side. Start from the top. Give the article a name, and make sure the slug looks correct. ** '''What is the slug?''' The slug is part of the url of the article, like: http://support.mozilla.org/en-US/kb/this-is-the-slug. It shouldn't exceed 50 characters. From the auto-generated slug, you can remove stop words and other unnecessary words. Make sure it stays human-readable (= easy to understand for humans) and has the most important information. * Translate the keywords for the article. ** '''Why should I translate the keywords?''' An article must be easily findable. That's the role of keywords. All words in the title that are not English [https://en.wikipedia.org/wiki/Stop_words stop words] such as "the" and "is" are already considered as keywords, so don't add them as keywords. Depending on your locale, translate some or all the keywords and eventually add synonyms, related terms, regional versions, usual typos, and usual anglicisms. DO NOT add too many keywords because each one of them will have less weight. For more info, see [[When and how to use keywords to improve an article's search ranking]]. * Then, translate the search results summary. Try to find a compromise between an accurate translation and the 160-character limit. ** '''What is the search summary?''' The text paragraph that is listed on the search results page. Make sure it gives people who search for help a clear idea of what they can find when they click the article. * Finally, move on to the full article text. Translate everything that is '''not''' within brackets like these: [ { } ]. Be careful about the product UI label translation. ** '''Why should I be careful?''' The product UI is usually not translated by you. In order to know what is the chosen label, use the [http://transvision.mozfr.org/ Transvision glossary]. If you are unsure what something means, you should read about '''[[How to use For]]''' and '''[[How to use Templates]]''' to learn more about those elements. Also, remember to ask your Locale Leaders or other localizers for help. * When you are done, submit the article for review, and make sure you add a meaningful comment, as it will be displayed on the article history page. {note}Remember that the review may take some time, so be patient and move on to another article, if you have the time.{/note} That's it! You translated your first article - thank you! We hope you find it easy enough to translate more than one :-). If you enjoyed it and want to keep translating articles into your language, you should read the following article: [[How do I update articles after their first translation?]] Remember that you should always ask your Locale Leaders or other localizers for help if you don't know or understand something. We all learn from one another and make each other greater - that's the essence of open source! {note}Do you have any questions? Do you need assistance while localizing? Please tell us on the [/forums/l10n-forum l10n forum].{/note}
==Who do I talk to if I have questions?== At some point we were all new to localizing in SUMO, so having questions is welcome and encouraged. The more you ask, the more you know! To get answers, you should find the right people to talk to. You can find us at the following places: * [https://client00.chat.mibbit.com/?server=irc.mozilla.org&channel=%23sumo-1l0ns #/sumo-l10ns channel] on IRC * [https://client00.chat.mibbit.com/?server=irc.mozilla.org&channel=%23sumo #sumo channel] on IRC * [https://support.mozilla.org/forums/l10n-forum/ SUMO l10n forum] on this site You should also stay in touch with your Locale Leaders. You can find them by [https://support.mozilla.org/kb/locales going to the locale list] and clicking your language in the list. Your Locale Leaders are the best people to ask for advice and most up-to-date information regarding the localization of SUMO into your language. === Translating an article === {note}'''IMPORTANT:''' The information below is universal to all locales. To get detailed information about localizing into your language, please get in touch with your Locale Leaders - they will tell you what style of language to use and what to look out for. Thank you!{/note} * Go to [/localization your localization dashboard]. <!-- SCREENSHOT GOES HERE --> * At the very top there is a list of the most visited articles. Pick and click the first article you see marked with a red triangle, expand {menu Editing Tools} on the left, and then click {menu Translate Article}. <!-- SCREENSHOT GOES HERE --> * On the next page the English version is displayed on the left hand side, the translation goes into the right hand side. Start from the top. Give the article a name, and make sure the slug looks correct. ** '''What is the slug?''' The slug is part of the url of the article, like: http://support.mozilla.org/en-US/kb/this-is-the-slug. It shouldn't exceed 50 characters. From the auto-generated slug, you can remove stop words and other unnecessary words. Make sure it stays human-readable (= easy to understand for humans) and has the most important information. * Translate the keywords for the article. ** '''Why should I translate the keywords?''' An article must be easily findable. That's the role of keywords. All words in the title that are not English [https://en.wikipedia.org/wiki/Stop_words stop words] such as "the" and "is" are already considered as keywords, so don't add them as keywords. Depending on your locale, translate some or all the keywords and eventually add synonyms, related terms, regional versions, usual typos, and usual anglicisms. DO NOT add too many keywords because each one of them will have less weight. For more info, see [[When and how to use keywords to improve an article's search ranking]]. * Then, translate the search results summary. Try to find a compromise between an accurate translation and the 160-character limit. ** '''What is the search summary?''' The text paragraph that is listed on the search results page. Make sure it gives people who search for help a clear idea of what they can find when they click the article. * Finally, move on to the full article text. Translate everything that is '''not''' within brackets like these: [ { } ]. Be careful about the product UI label translation. ** Do '''not''' translate the English article titles referenced in the page (they are framed with double square [[ ]] brackets). They will automatically update to your locale when you localize the target page into your locale. ** '''Why should I be careful?''' The product interface (also known as UI) is translated outside of SUMO. In order to know what is the chosen label for each UI component (for example, a button in Firefox or a menu in Firefox OS), use the [http://transvision.mozfr.org/ Transvision glossary search]. If you are unsure what something means, you should read about '''[[How to use For]]''' and '''[[How to use Templates]]''' to learn more about those elements. Also, remember to ask your Locale Leaders or other localizers for help. * When you are done, submit the article for review, and make sure you add a meaningful comment, as it will be displayed on the article history page. {note}Remember that the review may take some time, so be patient and move on to another article, if you have the time.{/note} That's it! You translated your first article - thank you! We hope you find it easy enough to translate more than one :-). If you enjoyed it and want to keep translating articles into your language, you should read the following article: [[How do I update articles after their first translation?]] Remember that you should always ask your Locale Leaders or other localizers for help if you don't know or understand something. We all learn from one another and make each other greater - that's the essence of open source! {note}Do you have any questions? Do you need assistance while localizing? Please tell us on the [/forums/l10n-forum l10n forum].{/note}

Back to History