1
edit
Nepal/Localization/Localization Style Guide: Difference between revisions
Nepal/Localization/Localization Style Guide (view source)
Revision as of 09:28, 27 August 2023
, 27 August 2023→Formality, Tone and Natural Expression: replaced 'आ' character
(Added information about wordlist, translation consistency) |
(→Formality, Tone and Natural Expression: replaced 'आ' character) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 17: | Line 17: | ||
[x] Do not translate it as ''"वाह! कस्ता राम्रा जुत्ताका जोडा।"'' | [x] Do not translate it as ''"वाह! कस्ता राम्रा जुत्ताका जोडा।"'' | ||
[✔] But 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. | 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. | ||
| Line 108: | Line 108: | ||
Zip code/Postal code is not widely used. Exact addressing is limited to certain places only. There is no any defined format as of now. | Zip code/Postal code is not widely used. Exact addressing is limited to certain places only. There is no any defined format as of now. | ||
=== Word Forms === | |||
<big> Pluralization </big> | |||
Please refer to the standard Unicode Plural specification for Nepali language (http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#ne). | |||
When using plural verbs, use आ sound, instead अ sound which is used for singular verbs. Same rule applies for adjectives too. | |||
Nepali language uses plural form #2 as specified in the following link: https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals | |||
Singular: 1 | |||
Plural: 0, 0.0 - 0.9, 1.1 - ... , 2,3,4,5,... | |||
<big> User Interface Elements </big> | |||
* Titles : Should be brief and precise. Localizers can assume that source content reaches 2/3 of the total available line space. This allows localization text to expand and not be truncated or resolved through ellipsis. Title on the final page (meaning no more click through) should allow enough room to display full text. | |||
* Buttons: Capitalize the first letter of each word. Limit to one or two words. Use verbs that precisely describe the button's action. For example, "Cancel", "Clear History", "Add Email", "Select All", etc. | |||
Value Selector Lists: Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words. | |||
* Articles: Avoid them where possible. Articles (such as the word "the" in English) should be avoided wherever possible. User interface elements have limited space available for text. Avoiding articles will help ensure that your translations will be accommodated within the user interface. | |||
*Ellipsis: Ellipsis are often inserted automatically in the UI where strings are truncated. Ellipsis should only be used at high level of UI pages, but not be on the final page (after a series of click-through) where detailed instruction is given. Ellipsis should not be used as a way to solve truncation issue. Focus on making the UI short and precise. The sequence of the sentence structure in another language may not translate well, when a sentence is half finished as such. | |||
== Translation Consistency == | == Translation Consistency == | ||