Localization/en - Revision history

FuzzyBot: Updating to match new version of source page

2020-10-08T19:52:10Z

Updating to match new version of source page

← Older revision		Revision as of 21:52, 8 October 2020
Line 11:		Line 11:
	=== Languages for administration interface and built-in messages for survey participants===		=== Languages for administration interface and built-in messages for survey participants===

	The public survey screens and the admin interface can be localized so that built-in messages and text appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the German language version. LimeSurvey has ~~about~~ 50 different languages of built-in messages already translated. To see the translation status for these languages please ~~follow~~ the link:		The public survey screens and the admin interface can be localized so that built-in messages and text appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the German language version. LimeSurvey has more than 50 different languages of built-in messages already translated. To see the translation status for these languages please select your LimeSurvey version from the link:

	[https://~~www~~.limesurvey.org/en/~~community-services/contribute/translations-status~~ LimeSurvey - Translations Status]		[https://translate.limesurvey.org/projects/ LimeSurvey - Translations Status]

	You can create/update your own translation locally by using these instructions:		You can create/update your own translation locally by using these instructions:

FuzzyBot: Updating to match new version of source page

2017-11-07T10:35:02Z

Updating to match new version of source page

← Older revision		Revision as of 12:35, 7 November 2017
Line 7:		Line 7:
	One is in the installation directory where built-in messages to the PHP code are stored in language specific files. These must be translated and installed by the system administrator. Only then is the language available for the administrative interface, for some basic buttons, and built-in messages seen by survey participants. Normally, a survey developer would not have access to edit these translations, but only select them.		One is in the installation directory where built-in messages to the PHP code are stored in language specific files. These must be translated and installed by the system administrator. Only then is the language available for the administrative interface, for some basic buttons, and built-in messages seen by survey participants. Normally, a survey developer would not have access to edit these translations, but only select them.

	The other source of language specific localization is in the surveys themselves. These translations for each survey consist of the survey title, overview, ~~and each~~ group, question, answer, and label set text. All these translations are stored in SQL database tables. Normally, a survey developer must define all the desired translations beside the base language.		The other source of language specific localization is in the surveys themselves. These translations for each survey consist of the survey title, overview, question group, question, answer and label set text. All these translations are stored in SQL database tables. Normally, a survey developer must define all the desired translations beside the base language.

	=== Languages for administration interface and built-in messages for survey participants===		=== Languages for administration interface and built-in messages for survey participants===

	The public survey screens and the admin interface can be localized so that built-in messages and text appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the ~~Deutsch/~~German version. LimeSurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:		The public survey screens and the admin interface can be localized so that built-in messages and text appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the German language version. LimeSurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:

	[https://www.limesurvey.org/en/community-services/contribute/translations-status LimeSurvey - Translations Status]		[https://www.limesurvey.org/en/community-services/contribute/translations-status LimeSurvey - Translations Status]
Line 21:		Line 21:
	If you want to update an existing translation, please consider contributing it for future releases (Read: [https://www.limesurvey.org/en/community-services/contribute/translations-status Translations status]). If you only update your version, remember to take care of this when you upgrade later.		If you want to update an existing translation, please consider contributing it for future releases (Read: [https://www.limesurvey.org/en/community-services/contribute/translations-status Translations status]). If you only update your version, remember to take care of this when you upgrade later.

	<div class="simplebox">'''Note:'''The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, put the text in other objects (e.g. questions and/or question groups) that are localized.</div>		<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, put the text in other objects (e.g. questions and/or question groups) that are localized.</div>

	So far, we only discussed translating the built-in text of the administration interface that the survey participants and developers see; ~~that~~ part that is independent of any survey. Each survey can have one or more languages associated with it. The language of the survey can be independent of the one used in the interface. So care must be taken to offer the appropriate translations there as well.		So far, we only discussed translating the built-in text of the administration interface that the survey participants and developers see; the part that is independent of any survey. Each survey can have one or more languages associated with it. The language of the survey can be independent of the one used in the interface. So care must be taken to offer the appropriate translations there as well.

	=== Languages for surveys themselves===		=== Languages for surveys themselves===

FuzzyBot: Updating to match new version of source page

2017-09-11T09:05:03Z

Updating to match new version of source page

← Older revision		Revision as of 11:05, 11 September 2017
Line 1:		Line 1:

	<languages />		<languages />
	~~There are two places where language specific localization are defined and stored.~~		=General=

	~~One is in the Installation directory~~ where ~~built-in messages to the PHP code are stored in~~ language specific ~~files. These must be translated and installed by the system administrator before that language~~ is ~~available for the administrative interface~~ and ~~for some basic buttons and built-in messages seen by survey participants. Normally, a survey developer would not have access to edit but only select these translations~~.		There are two places where language specific localization is defined and stored.

	~~The other source of~~ language specific ~~localization~~ is in the ~~surveys themselves. These translations~~ for ~~each survey consist of~~ the ~~survey title~~, ~~overview~~, and ~~each group, question, answer and labelset text. All these translations are stored~~ in ~~the SQL database tables themselves~~. ~~Normally~~, a survey developer ~~must define all the desired~~ translations ~~beyond the base language~~.		One is in the installation directory where built-in messages to the PHP code are stored in language specific files. These must be translated and installed by the system administrator. Only then is the language available for the administrative interface, for some basic buttons, and built-in messages seen by survey participants. Normally, a survey developer would not have access to edit these translations, but only select them.

	~~=== Languages~~ for ~~administration interface and built-~~in ~~messages for~~ survey ~~participants===~~		The other source of language specific localization is in the surveys themselves. These translations for each survey consist of the survey title, overview, and each group, question, answer, and label set text. All these translations are stored in SQL database tables. Normally, a survey developer must define all the desired translations beside the base language.

	~~The public survey screens and the admin~~ interface ~~can be localized so that built-in messages and text will appear in your preferred language. For example "yes" and "no" would appear as "ja"~~ and ~~"nein" in the Deutsch/German version. LimeSurvey has about 50 different languages of~~ built-in messages ~~already translated. To see the translation status~~ for ~~these languages please follow the link:~~		=== Languages for administration interface and built-in messages for survey participants===

	~~[https:/~~/~~www~~.~~limesurvey~~.~~org/en/community-services/contribute/translations-~~status ~~Translations Status]~~		The public survey screens and the admin interface can be localized so that built-in messages and text appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the Deutsch/German version. LimeSurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:

	You can create/update your own translation locally by using these instructions:		[https://www.limesurvey.org/en/community-services/contribute/translations-status LimeSurvey - Translations Status]

			You can create/update your own translation locally by using these instructions:

	[[How to translate LimeSurvey]]		[[How to translate LimeSurvey]]

	If you want to update an existing translation, please consider contributing it for future releases (Read: [https://www.limesurvey.org/en/community-services/contribute/translations-status Translations ~~Status~~]). If you only update your version, remember to take care of this when you upgrade later.		If you want to update an existing translation, please consider contributing it for future releases (Read: [https://www.limesurvey.org/en/community-services/contribute/translations-status Translations status]). If you only update your version, remember to take care of this when you upgrade later.

	<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. ~~Try~~ to avoid putting text directly into the template files. ~~Instead~~, ~~define~~ the ~~necessary language~~ in other ~~files~~ that are localized.</div>		<div class="simplebox">'''Note:'''The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, put the text in other objects (e.g. questions and/or question groups) that are localized.</div>

	So far we only discussed translating the built-in text of the administration interface that the survey participants and developers see; that part that is independent of any survey. ~~Each~~ survey can have one or more languages associated with it ~~as well~~ independent of ~~this~~ interface. So care must be taken to offer the appropriate translations there as well.		So far, we only discussed translating the built-in text of the administration interface that the survey participants and developers see; that part that is independent of any survey. Each survey can have one or more languages associated with it. The language of the survey can be independent of the one used in the interface. So care must be taken to offer the appropriate translations there as well.

	=== Languages for surveys themselves===		=== Languages for surveys themselves===

	If more than one language is defined for a survey, ~~then~~ when editing that survey or each question, answer or ~~labelset~~ within it -- you ~~then~~ need to make sure to add all the language translations desired. ~~Otherwise~~, the default language of the survey will appear if no translation is available. ~~This~~ is available when editing a ~~Survey~~, ~~Group~~, ~~Question~~, ~~Answer~~ set or ~~labelset~~.		If more than one language is defined for a survey, when editing that survey (or each question, answer or label set within it), you need to make sure to add all the language translations desired. Otherwise, the default language of the survey will appear if no translation is available. This is available when editing a survey, group, question, answer set or label set.

	<div class="simplebox">'''Note:''' If you do not have permission to edit ~~labelsets~~, you will not be able to provide the translation of that ~~labelset~~ either. ~~Talk~~ to your survey administrator about either giving you the permission to edit the ~~labelset~~ or providing the translation in your desired language.</div>		<div class="simplebox">'''Note:''' If you do not have the permission to edit label sets, you will not be able to provide the translation of that label set either. Talk to your survey administrator about either giving you the permission to edit the label set or providing the label set translation in your desired language.</div>

FuzzyBot: FuzzyBot moved page Localisation/en to Localization/en without leaving a redirect: Part of translatable page "Localisation".

2017-09-06T08:40:04Z

FuzzyBot moved page Localisation/en to Localization/en without leaving a redirect: Part of translatable page "Localisation".

← Older revision		Revision as of 10:40, 6 September 2017
(No difference)

FuzzyBot: Importing a new version from external source

2017-01-25T10:38:39Z

Importing a new version from external source

← Older revision		Revision as of 12:38, 25 January 2017
Line 11:		Line 11:
	The public survey screens and the admin interface can be localized so that built-in messages and text will appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the Deutsch/German version. LimeSurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:		The public survey screens and the admin interface can be localized so that built-in messages and text will appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the Deutsch/German version. LimeSurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:

	[~~http~~://www.limesurvey.org/en/contribute/translations-status Translations Status]		[https://www.limesurvey.org/en/community-services/contribute/translations-status Translations Status]

	You can create/update your own translation locally by using these instructions:		You can create/update your own translation locally by using these instructions:

FuzzyBot: Importing a new version from external source

2017-01-25T10:15:43Z

Importing a new version from external source

← Older revision		Revision as of 12:15, 25 January 2017
Line 17:		Line 17:
	[[How to translate LimeSurvey]]		[[How to translate LimeSurvey]]

	If you want to update an existing translation, please consider contributing it for future releases (Read: [~~http~~://www.limesurvey.org/en/contribute/translations-status Translations Status]). If you only update your version, remember to take care of this when you upgrade later.		If you want to update an existing translation, please consider contributing it for future releases (Read: [https://www.limesurvey.org/en/community-services/contribute/translations-status Translations Status]). If you only update your version, remember to take care of this when you upgrade later.

	<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, define the necessary language in other files that are localized.</div>		<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, define the necessary language in other files that are localized.</div>

FuzzyBot: Importing a new version from external source

2013-10-07T13:57:50Z

Importing a new version from external source

← Older revision		Revision as of 15:57, 7 October 2013
Line 17:		Line 17:
	[[How to translate LimeSurvey]]		[[How to translate LimeSurvey]]

	If you ~~do modify or create a new~~ translation, please consider contributing it for future releases. ~~Also, if~~ you ~~do modify or create a new translation~~, remember to take care of this when upgrade ~~to a newer version~~ later.		If you want to update an existing translation, please consider contributing it for future releases (Read: [http://www.limesurvey.org/en/contribute/translations-status Translations Status]). If you only update your version, remember to take care of this when you upgrade later.

	<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, define the necessary language in other files that are localized.</div>		<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, define the necessary language in other files that are localized.</div>

C schmitz: Text replace - "Limesurvey" to "LimeSurvey"

2013-06-06T13:19:44Z

Text replace - "Limesurvey" to "LimeSurvey"

← Older revision		Revision as of 15:19, 6 June 2013
Line 9:		Line 9:
	=== Languages for administration interface and built-in messages for survey participants===		=== Languages for administration interface and built-in messages for survey participants===

	The public survey screens and the admin interface can be localized so that built-in messages and text will appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the Deutsch/German version. ~~Limesurvey~~ has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:		The public survey screens and the admin interface can be localized so that built-in messages and text will appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the Deutsch/German version. LimeSurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:

	[http://www.limesurvey.org/en/contribute/translations-status Translations Status]		[http://www.limesurvey.org/en/contribute/translations-status Translations Status]

FuzzyBot: Importing a new version from external source

2013-04-08T23:43:34Z

Importing a new version from external source

New page

<languages />
There are two places where language specific localization are defined and stored.

One is in the Installation directory where built-in messages to the PHP code are stored in language specific files. These must be translated and installed by the system administrator before that language is available for the administrative interface and for some basic buttons and built-in messages seen by survey participants. Normally, a survey developer would not have access to edit but only select these translations.

The other source of language specific localization is in the surveys themselves. These translations for each survey consist of the survey title, overview, and each group, question, answer and labelset text. All these translations are stored in the SQL database tables themselves. Normally, a survey developer must define all the desired translations beyond the base language.

=== Languages for administration interface and built-in messages for survey participants===

The public survey screens and the admin interface can be localized so that built-in messages and text will appear in your preferred language. For example "yes" and "no" would appear as "ja" and "nein" in the Deutsch/German version. Limesurvey has about 50 different languages of built-in messages already translated. To see the translation status for these languages please follow the link:

[http://www.limesurvey.org/en/contribute/translations-status Translations Status]

You can create/update your own translation locally by using these instructions:

[[How to translate LimeSurvey]]

If you do modify or create a new translation, please consider contributing it for future releases. Also, if you do modify or create a new translation, remember to take care of this when upgrade to a newer version later.

<div class="simplebox">'''Note:''' The template files are not currently localized and thus are language independent. Try to avoid putting text directly into the template files. Instead, define the necessary language in other files that are localized.</div>

So far we only discussed translating the built-in text of the administration interface that the survey participants and developers see; that part that is independent of any survey. Each survey can have one or more languages associated with it as well independent of this interface. So care must be taken to offer the appropriate translations there as well.

=== Languages for surveys themselves===

If more than one language is defined for a survey, then when editing that survey or each question, answer or labelset within it -- you then need to make sure to add all the language translations desired. Otherwise, the default language of the survey will appear if no translation is available. This is available when editing a Survey, Group, Question, Answer set or labelset.

<div class="simplebox">'''Note:''' If you do not have permission to edit labelsets, you will not be able to provide the translation of that labelset either. Talk to your survey administrator about either giving you the permission to edit the labelset or providing the translation in your desired language.</div>