Translate your configurators to different languages to reach an international audience.
Localizing Names & Descriptions
To localize the names and descriptions of all items in the configurator to new languages, follow these steps:
1. Setup the language in the company settings
To add translations of a specific language to your configurator, you must first have added this language to your company settings. Learn how
2. Open the translate dialog for your configurator
In the configurator admin screen, click on the 'Translate' button in the bottom toolbar.
3. Add translations for your configurator objects
The translation dialog will show a list of all the items (and their properties) in the configurator that can be translated. There will be a column showing your terms for these items in your default language, and a column for each additional language you have chosen to support in your company settings.
4. Save your translations
Missing translations that need your attention are shown in red. To add missing translations, select the cell in the table and start typing. You can also auto-translate all the missing translations by clicking on the 'Auto-Translate' button, which will use the Google Translate API to fill in your missing translations, which you can further edit.
Localizing Options from an Option Filter
Localizing Output Documents
Machine translations should be reviewed.
If you use "auto-translate", be aware that the translations come from a machine algorithm, not a person fluent in that language. The words may not be accurate. Have a native speaker review and confirm automated
translations before you deploy your changes.
1. Create an output document for each locale
To save your translations, click on 'OK', and then save the configurator. Note that if later you add more fields, actions, etc. to the configurator, you should also come back to the translations dialog and add the missing translations for them. Missing entries will again be highlighted in red.
2. Store the user's locale
To localize the options in select boxes, we add localized columns to the Tables or Database Tables that are driving the option filter. If your option filter is based on a query, you should also make sure the localized columns are included in the result (meaning you need to include them in your select clause of the query if you have one).
3. Use that stored locale to activate the correct output document
If you localize a configurator, it is strongly suggested that you use option filters to drive your select controls. If you drive those options through Snap rules, then you will be making your life much harder!
Learn how to localize Table columns
Learn how to localize Database Table columns
To localize an output document, such as a quote or a bill of material (BOM), first ensure you have a working output document in your base language. Then follow these steps:
Duplicate your existing document, and edit it to match the needs of the particular language. You'll replace the text, of course, as well as make any formatting adjustments. Remember to focus on language changes. Don't focus on geographic changes, such as how shipping fees are different when selling to Spain vs. Mexico vs. Ecuador in your "ES" Spanish template.
Save those documents under your existing build. For example, if your "Sales" build was in English before, it's in 3 languages now:
Create a hidden field in your configurator (here, we call it "theClientLanguage"). Then create a Loaded Rule that fills this hidden field with the user's locale:
Why do we do this? The get block that offers you the clientLanguage is available only when the configurator is running in your user's browser. When your user leaves the page or closes her browser, the UI no longer exists. Therefore, the clientLanguage of that browser also disappears. If we store it, however, then we can access it in later processes or server-based processes, like sending email messages or generating output documents.
Now that you've stored the user's locale, you can use it in the future after the user has closed the browser window and walked away. For example, you can use that stored locale in an output rule for your German version of the BOM in your "Sales" build:
