Getting started<\/h2>\n\n\n\n
As a first step you’ll create a dictionary for each language that you want to use in your survey campaigns. You can create a dictionaries in the global settings of your environment under SETTINGS > TRANSLATIONS.<\/p>\n\n\n\n
A dictionary consists of a name, a unique identifier, the text reading direction (LTR \/ RTL), and the actual text translations. <\/p>\n\n\n
![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2022\/06\/Screenshot-2022-06-28-at-23.26.39-1024x649.png\")
<\/figure><\/div>\n\n\nWe recommend to use two letter ISO 639-1 language codes<\/a> (e.g. en, fr, de, …) as the language identifiers of your dictionaries.<\/p>\n\n\n\n If you use the standardized two letter format, the translation of surveys will work seamlessly without the need to change any code. <\/p>\n\n\n\n You can also use custom language codes, for example if your app stores languages codes in a different format. In this case, you’ll need to set the language identifiers for each user as described further below.<\/p>\n\n\n\n Once you created a couple of dictionaries, you are ready to start translating your surveys.<\/p>\n\n\n\n Refiner allows you to quickly create, adjust and verify translations while you are are creating a survey.<\/p>\n\n\n\n If your user profile has the necessary rights and if at least one dictionary was created, you’ll see an earth symbol next to all form inputs with translatable text. The symbol appears in green if translations for all languages are available and in red when translations are missing.<\/p>\n\n\n When you click on the earth symbol, you’ll access a modal to translate this particular text item. The translation you provide in the modal will be used for all surveys in your environment that are using the exact same text.<\/p>\n\n\n Next to translating surveys as you create them, you can also use the Translation Hub to manage all dictionaries and translations in one central place. You can find the Translation Hub in the settings of your Refiner environment.<\/p>\n\n\n Each text token used in your surveys is represented as a table row, with the original text in the first column. This list is generated automatically and includes all text tokens that are currently used in your surveys. You can think of this list as your default language.<\/p>\n\n\n\n Translating a text token will provide a translation for all surveys using this specific text.<\/p>\n\n\n\n You can either translate text fragments row by row, or work your way through the matrix column by column. <\/p>\n\n\n Missing translations are marked with a red background. If a translation for a text fragment is not available, the default language of the survey is used as fallback<\/p>\n\n\n\n Next to translating text tokens manually you can choose to let AI do the heavy lifting. With a simple click of a button, Refiner AI translates all missing text tokens for you.<\/p>\n\n\n\n The AI translation feature is available both in the Translation Hub and directly within the survey editor while creating or editing a survey.<\/p>\n\n\n To make AI Translations work reliable, please use common english language names (e.g. German, French, Italian, \u2026) for your dictionaries<\/p>\n\n\n\n When the translation feature is enabled for your account, you’ll see a language switcher in the top right section of the survey editor. Changing the language here will automatically translate the survey preview. <\/p>\n\n\n Customer using a third party service for translations can export and import dictionaries in JSON format.<\/p>\n\n\n\n The JSON file allows customer to use dedicated translation tools, or outsource the translation process to third parties without giving them access to your Refiner account.<\/p>\n\n\n If you stick to the ISO 639-1 norm for your dictionary slugs (e.g. fr<\/em> for French, de<\/em> for German, …), translations are provided seamlessly by detecting the preferred web browser language of your user.<\/p>\n\n\n\n If you are using custom language codes, or if you simply want to explicitly set the user language, please use the setLocale<\/em> method as described here<\/a>.<\/p>\n\n\n\n Whenever you identify a mobile app users with the “identifyUser” method, you’ll also provide a locale<\/em> value as described here<\/a>.<\/p>\n\n\n\n If you stick to the ISO 639-1 norm for your dictionary slugs (e.g. fr<\/em> for French, de<\/em> for German, …), translations are provided seamlessly by detecting the preferred web browser language of your user.<\/p>\n\n\n\n You can explicitly set the language of a Survey Page by providing a “locale” URL parameter as described here<\/a>.<\/p>\n\n\n\n If you stick to the ISO 639-1 norm for your dictionary slugs (e.g. fr<\/em> for French, de<\/em> for German, …), translations are provided seamlessly by detecting the preferred web browser language of your user.<\/p>\n\n\n\n You can choose to explicitly set the language of a Email Survey Page when generating the HTML embed code as described here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Introduction Refiner comes equipped with a powerful dictionary based translation system. You can create a dictionary for every language for which you would like to provide translations. In case of a missing translation, the survey will be shown in its original language as a fallback. On this page we’ll describe how to create dictionaries, translate […]<\/p>\nTranslate survey<\/h2>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2023\/10\/Screenshot-2023-10-19-at-13.36.53.png\")
<\/figure><\/div>\n\n\n![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2023\/09\/Screenshot-2023-09-22-at-12.17.54-1024x539.png\")
<\/figure><\/div>\n\n\nTranslation Hub<\/h2>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2022\/06\/Screenshot-2022-06-28-at-23.25.56-1024x562.png\")
<\/figure><\/div>\n\n\n![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2022\/06\/Screenshot-2022-06-28-at-23.27.41-1024x241.png\")
<\/figure><\/div>\n\n\nTranslate with AI<\/h2>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2021\/04\/Screenshot-2026-02-23-at-16.33.02-1024x690.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2021\/04\/Screenshot-2026-02-23-at-16.34.09-1024x657.png\")
<\/figure><\/div>\n\n\nPreview translated surveys<\/h2>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2022\/02\/Screenshot-2022-02-19-at-00.11.34-1024x517.png\")
<\/figure><\/div>\n\n\nImport & export dictionaries<\/h2>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2023\/10\/Screenshot-2023-10-12-at-15.55.21-1-1024x389.png\")
<\/figure><\/div>\n\n\nSet user language<\/h2>\n\n\n\n
JavaScript SDK<\/h3>\n\n\n\n
Mobile SDK<\/h3>\n\n\n\n
Survey Pages<\/h3>\n\n\n\n
Email Surveys<\/h3>\n\n\n\n