Nepal/Localization/Localization Style Guide

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!"

[x] 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.

Cultural References

If the source language has a cultural reference that has no equivalent and widely accepted Nepali phrase, remove the cultural reference and translate the core meaning.

Brand Names

All Brand Names are kept in it’s original language and never translated. For example do not translate "Firefox", "Mozilla", "Facebook", "Twitter", "Skype", anything that is a name of a brand.

Technical Strings

Strings which are part of a library specification, some complex words and phrases which gives meaning only on the context of the specific library or language should not be translated. This will be changed slowly when local developer start shifting their programming paradigm to the local language, in which case, we will slowly translate those english strings to nepali. But for this, a detailed meeting with list of words to translate to nepali will be published.

Short Forms

This is different from abbreviations, which are generally not translated but again depends on context. Short Forms such as prefs: for preferences will be elongated while translating to Nepali. This means that prefs: will be translated to प्राथमिकता and not प्रेफ्स:

MDN Links

When you are introduced with MDN Links, remove the `en-US/` part of the URL so that the URL redirects to the proper locale. Example. https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Encryption becomes https://developer.mozilla.org/docs/Web/API/Push_API/Using_the_Push_API#Encryption

Translating Legal Strings

When translating somewhat legal strings(about:rights, licenses), pay special care to translate to corresponding legal Nepali tone.

Terminology

Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):

• Microsoft key terms and target languages https://www.microsoft.com/Language/en-US/Default.aspx
• Pootle's own term list: https://mozilla.locamotion.org/ne/terminology/essential.po

You should be consistent in the use of existing reliable appropriate term bases in nepali language. These term bases could be developed and approved by the Mozilla Nepal community, or leveraged from another party that adhere to national, international or local standards for software and internet terminology. Avoid the following:

• Inconsistent use of terminology within the project
• Inconsistent use of terminology with term base
• Inconsistent use of terminology across all of your projects
• Using terminology from another subject matter (e.g., don't use medical terminology in Firefox).