Confirmed users
29
edits
Nepal/Localization/Localization Style Guide: Difference between revisions
Nepal/Localization/Localization Style Guide (view source)
Revision as of 07:44, 26 November 2016
, 26 November 2016Added Word Forms.
(Added information about wordlist, translation consistency) |
(Added Word Forms.) |
||
| 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. | ||
== Units and Grammar == | |||
The translation should strive to achieve proper unit conversions for currency, measurements, etc. for the target audience. | |||
=== Units and Unit Conversion === | |||
<big> Date Format </big> | |||
The date formats for weeks and months can be expressed in the following forms: | |||
* Fully spelled out | |||
* Two or Three letters | |||
* Single letter | |||
While localizing Dates, use the format by taking into consideration about the target space available. | |||
Reference material can be found here: https://en.wikipedia.org/wiki/Date_format_by_country | |||
<big> Calendar view: </big> | |||
* Sunday should be the first day of the week. | |||
* Even though lunar calendar is used in our daily life, we should follow Gregorian calendar for localization. | |||
Regional Calendar is Observed. The calendar in use is “Bikram Sambat”, about 47 years ahead of A.D. (See: http://nepalipatro.com.np ) | |||
<big> Time Format </big> | |||
HH:MM <time of day> (12 hour clock) is the preferred Time format. | |||
<big> Numerals </big> | |||
Use comma as a separator. Use Nepali system. eg Rs 1,000 & 1,00,00,000 | |||
<big> Currency </big> | |||
Google App Store currently shows “NPR” as the currency to buy its apps. It is the standard currency code, we do not have any notations. | |||
<big> Units </big> | |||
If Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to metric measurement system. | |||
<big> Names </big> | |||
The order of name is: Prefix FirstName MiddleName LastName | |||
<big> Address and Postal Code Format </big> | |||
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 == | ||