Nepal/Localization/Localization Style Guide: Difference between revisions
(Created page with "==Mozilla L10n Style Guide for ne_np== <big>'''Intro'''</big> Style guides define the standard against which we determine a translation's quality. They contain rules that a...") |
No edit summary |
||
| Line 1: | Line 1: | ||
<big>'''Mozilla L10n Style Guide for ne_np'''</big> | |||
<big> | <big>Intro</big> | ||
Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla Nepal on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture. | Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla Nepal on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture. | ||
| Line 21: | Line 21: | ||
Also, complete sentences are preferred over incomplete english counterparts whenever space is not strictly constrained. For example, when translating About &brandShortName; preference is given to &brandShortName; को बारेमा जान्नुहोस् over &brandShortName; बारे . When space is a problem, (maybe in mobile?), find closest-to-complete phrase which is shorter in length. For the above example, it could be &brandShortName; को बारेमा . Always keep in mind that “easy-for-users-to-understand” is given preference over “because-there-was-no-space” translations. | Also, complete sentences are preferred over incomplete english counterparts whenever space is not strictly constrained. For example, when translating About &brandShortName; preference is given to &brandShortName; को बारेमा जान्नुहोस् over &brandShortName; बारे . When space is a problem, (maybe in mobile?), find closest-to-complete phrase which is shorter in length. For the above example, it could be &brandShortName; को बारेमा . Always keep in mind that “easy-for-users-to-understand” is given preference over “because-there-was-no-space” translations. | ||
== Cultural References == | |||
Revision as of 09:44, 24 September 2016
Mozilla L10n Style Guide for ne_np
Intro
Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla Nepal on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture.
Style
Formality, Tone and Natural Expression
The localization in Nepali language is expected to be formal. The target user of a browser falls under wide range of age groups, but the main reason for it to be formal is the nature of Nepali language. Since it sounds a bit odd to most of the people to read an informal nepali text on a standard software (happened before with Microsoft), it is advised to use formal language whenever possible.
The strong emphasis is given to "translate for meaning" and not to "translate word to word". For example, when getting a sentence like:
"Wow. Such Nice Pair of Shoes!"
Do not translate it as "वाह। यस्ता राम्रा जुत्ताका जोडा।"
But Translate it as "अाहा, कती राम्रो जुत्ता।"
Also, complete sentences are preferred over incomplete english counterparts whenever space is not strictly constrained. For example, when translating About &brandShortName; preference is given to &brandShortName; को बारेमा जान्नुहोस् over &brandShortName; बारे . When space is a problem, (maybe in mobile?), find closest-to-complete phrase which is shorter in length. For the above example, it could be &brandShortName; को बारेमा . Always keep in mind that “easy-for-users-to-understand” is given preference over “because-there-was-no-space” translations.