1
edit
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:28, 27 August 2023
, 27 August 2023→Formality, Tone and Natural Expression: replaced 'आ' character
m (→Word Forms: Minor changes in pages) |
(→Formality, Tone and Natural Expression: replaced 'आ' character) |
||
| 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. | ||