Create a multilingual project - field by field
Blue supports the distribution of questionnaires and reports in multiple languages based on user preference. See the list of languages supported by Blue.
Captions and messages can be translated field by field as the project is being created, or by using an XML file. Labels and captions can be added for multiple languages by selecting the language icon next to a field which opens the text editor.
In order for a user to automatically receive notifications in their preferred language, the user datasource must have a field that is properly mapped to the language field and the proper language code must be used. Language codes can be found in the list of language supported by Blue.
This topic explains how to configure a multilingual project and how to integrate translations field by field.
If the user’s preferred language is not supported in the project (as defined by the mapped language field in the user datasource), correspondence will be provided in all languages that the project supports. However, if the user doesn't specify a preferred language, the default language specified in the Blue license will be used..
Enable multilingual project support
In order to enable multiple languages in your project,
- Go to your project and select Info - Options
- Select Available Languages for this project
- Select the Base Language on which this project will default to
- Select Save Project
Blue will recognize the selected languages in its setup. Where available, the interface will automatically provide the translated content. These system fields will not require your intervention. However, there are labels that will require translations (detailed below).
- When filling in translations field by field, having the questionnaire translated in full before beginning the project may save you some time.
- When you have several questions using the same scale or question type, create a first question block and copy it as many times you need it. This will allow you to modify only the Question title, reducing the effort and time to build your questionnaire.
Anywhere you can enter text, a language tab (see en next to the content fields) allows you to launch the text editor. The text editor contains different tabs for each language.
Below is a list of the fields that require manual translation in a Blue project.
| Info | Questionnaire |
|---|---|
| Project Title | Section Heading/Section Titles |
| Project Description | Question Titles |
| Question Details | |
| Question Help | |
| Question 1st and 2nd Scale | |
| Question Scale Options | |
| Question Fillout |
| Definition | Tasks |
|---|---|
| Primary Subject Caption | Emails Subject |
| Secondary Subject Caption | Invitation Email Message and Subject |
| Groups Caption | 1st reminder Email Message and Subject |
| 2nd reminder Email Message and Subject | |
| Subsequent Email Subjects and Messages | |
| Welcome message | |
| Thank you message | |
| Task list info message | |
| Personalized question info message | |
| Rater selection message |
If you do not translate a field, the content will default to the base language. For example, if you have set a project with English (base language) and Spanish, and forgot to enter a Spanish Thank You Message, the English message will be displayed even if the rater selected Spanish as their preferred language.
- The content entered in the project is displayed in both questionnaires and reports by default. An alternative display called Fillout Labels Edit is available within the Question block. The question, details, and scale options entered in fillout labels will only display on the questionnaire.
- Fillout labels will not appear on reports. The use of fillout labels ensures that questionnaires are customized per user while still allowing aggregate style reports to be clean and easy to read.
- Fillout labels need to be translated too.
- Any missing values in the fillout labels will use the default content.
- Any missing translations in the fillout labels will use the base language content.
Use the XML language file
The second method of translating a project involves exporting the project's XML language file. It contains all the text that needs to be translated. The language file has a few potential uses:
- Translating the text into multiple languages
- Proofreading and reviewing
- Sending a spreadsheet to an external translator instead of giving Blue access to a third party
- Copying a project over to a new one
For more information on using the XML language file, consult Create a multilingual project - XML language file.
InInitial project creation
InFundamentals of Blue projects
InInitial project creation
InFundamentals of Blue
InInitial report creation