Actions

Localizzazione

From LimeSurvey Manual

Revision as of 12:34, 12 April 2017 by Aster93 (talk | contribs) (Created page with "Una è la cartella d'installazione dove i messaggi build-in nel codice PHP sono contenuti in specifici file di lingua. Questi devono essere tradotti ed installati prima che la...")

Ci sono due posti in cui la specifica localizzazione della lingua è definita è memorizzata.

Una è la cartella d'installazione dove i messaggi build-in nel codice PHP sono contenuti in specifici file di lingua. Questi devono essere tradotti ed installati prima che la lingua sia disponibile sull'interfaccia amministrativa e per alcuni pulsanti di base e per alcuni messaggi visualizzati dai partecipanti di un'indagine. Normalmente, lo sviluppatore di un sondaggio non ha accesso alla modifica ma solo alla sezione di queste traduzioni.

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:

Translations Status

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

How to translate LimeSurvey

If you want to update an existing translation, please consider contributing it for future releases (Read: Translations Status).  If you only update your version, remember to take care of this when you upgrade later.

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.

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.

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.