Confirmed users
29
edits
Nepal/Localization/Localization Style Guide: Difference between revisions
Jump to navigation
Jump to search
m
Nepal/Localization/Localization Style Guide (view source)
Revision as of 07:49, 26 November 2016
, 26 November 2016→Word Forms: Minor changes in pages
(Minor Edit) |
m (→Word Forms: Minor changes in pages) |
||
| Line 112: | Line 112: | ||
<big> Pluralization </big> | <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). | Please refer to the standard Unicode Plural specification for Nepali language (http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#ne). | ||
| Line 122: | Line 123: | ||
<big> User Interface Elements </big> | <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. | * 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. | ||
| Line 130: | Line 132: | ||
*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. | *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 == | ||