Confirmed users
19
edits
Nepal/Localization/Localization Style Guide: Difference between revisions
Jump to navigation
Jump to search
Nepal/Localization/Localization Style Guide (view source)
Revision as of 09:44, 24 September 2016
, 24 September 2016no edit summary
(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 == | |||