Nepal/Localization/Localization Style Guide - Revision history

Charismaticpilot: /* Formality, Tone and Natural Expression */ replaced 'आ' character

2023-08-27T09:28:27Z

Formality, Tone and Natural Expression: replaced 'आ' character

← Older revision		Revision as of 09:28, 27 August 2023
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.

Nootanghimire: /* Word Forms */ Minor changes in pages

2016-11-26T07:49:14Z

Word Forms: Minor changes in pages

← Older revision		Revision as of 07:49, 26 November 2016
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 ==

Nootanghimire: Minor Edit

2016-11-26T07:46:01Z

Minor Edit

@@ Line 60: / Line 60: @@
 *Inconsistent use of terminology across all of your projects
 *Using terminology from another subject matter (e.g., don't use medical terminology in Firefox).
 == Units and Grammar ==

Nootanghimire: Added Word Forms.

2016-11-26T07:44:52Z

Added Word Forms.

← Older revision		Revision as of 07:44, 26 November 2016
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 ==

Nootanghimire: Added information about wordlist, translation consistency

2016-11-26T03:58:04Z

Added information about wordlist, translation consistency

← Older revision		Revision as of 03:58, 26 November 2016
Line 49:		Line 49:
	Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):		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		* 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/		* Pootle's own term list: https://mozilla.locamotion.org/ne/terminology/
			* List of Nepali Words/Phrases and Explanation: https://docs.google.com/spreadsheets/d/1_2JeUCi3Bh-rgwc-426sXL0UvuNZ--diJuXQJcX-DHM/edit?usp=sharing


	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:		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:
Line 106:		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.

			== Translation Consistency ==
			Consistent Localization means that same source should have same translation whenever possible.

			We advise you to use Transvision (https://transvision.mozfr.org/consistency) to check for translation consistency and submit the translation.

			== General Mozilla L10n Style Guide ==
			You should also follow the guidelines in the following link while localizing Firefox.
			https://developer.mozilla.org/en-US/docs/L10n_Style_Guide#General_Mozilla_l10n_style

Nootanghimire: Fix Some Errors.

2016-11-26T03:24:01Z

Fix Some Errors.

← Older revision		Revision as of 03:24, 26 November 2016
Line 67:		Line 67:
	<big> Date Format </big>		<big> Date Format </big>

	~~How are the~~ date formats for weeks and months expressed in the following forms:		The date formats for weeks and months can be expressed in the following forms:

	*~~1).~~ Fully spelled out ~~2). 2~~ or 3 letters ~~3).~~ Single letter		* Fully spelled out
	*What is the order of Year, Month and Day?		* Two or Three letters
			* Single letter

	Reference material can be ~~find~~ here: https://en.wikipedia.org/wiki/Date_format_by_country		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>		<big> Calendar view: </big>

	*Sunday should be the first day of the week.		* 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.		* 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 )		Regional Calendar is Observed. The calendar in use is “Bikram Sambat”, about 47 years ahead of A.D. (See: http://nepalipatro.com.np )
Line 94:		Line 97:

	<big> Units </big>		<big> Units </big>
	~~Do you use the imperial, metric or nautical system for measuring weight, distance, etc.?~~ Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to ~~their~~ measurement system.		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>		<big> Names </big>

Nootanghimire: Minor Language Changes

2016-11-26T03:17:13Z

Minor Language Changes

← Older revision		Revision as of 03:17, 26 November 2016
Line 50:		Line 50:

	*Microsoft key terms and target languages https://www.microsoft.com/Language/en-US/Default.aspx		*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~~		*Pootle's own term list: https://mozilla.locamotion.org/ne/terminology/

	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:		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 within the project

Surit: Added content

2016-09-24T11:43:04Z

Added content

← Older revision		Revision as of 11:43, 24 September 2016
Line 58:		Line 58:
	*Inconsistent use of terminology across all of your projects		*Inconsistent use of terminology across all of your projects
	*Using terminology from another subject matter (e.g., don't use medical terminology in Firefox).		*Using terminology from another subject matter (e.g., don't use medical terminology in Firefox).

			== 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>

			How are the date formats for weeks and months expressed in the following forms:

			*1). Fully spelled out 2). 2 or 3 letters 3). Single letter
			*What is the order of Year, Month and Day?

			Reference material can be find 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>
			Do you use the imperial, metric or nautical system for measuring weight, distance, etc.? Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to their 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.

Avash at 11:39, 24 September 2016

2016-09-24T11:39:33Z

← Older revision		Revision as of 11:39, 24 September 2016
Line 1:		Line 1:
	<big>'''Mozilla L10n Style Guide for ne_np'''</big>		<big>'''Mozilla L10n Style Guide for ne_np'''</big>


	<big>Intro</big>		<big>Intro</big>
Line 16:		Line 15:
	"Wow. Such Nice Pair of Shoes!"		"Wow. Such Nice Pair of Shoes!"

	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.

	== Cultural References ==		== Cultural References ==

Surit at 10:34, 24 September 2016

2016-09-24T10:34:22Z

← Older revision		Revision as of 10:34, 24 September 2016
Line 47:		Line 47:

	== Terminology ==		== 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).