When you create interactive decision trees for many languages or dialects, you are reaching and helping more people.
Method 1: Tree Settings using Google Translate
Your decision tree can include these customizable Google Translate options. You'll find these controls in the tree's Settings > Languages tab:
- Tree Language: This is the language your tree was authored in. This option does not translate your entire tree. It's purpose is to translate only those Zingtree hard-coded text like the "Back" and "Restart" buttons. Choosing the option called "other" will replace the Back and Restart text with icons only.
- Locale for Date Picker: Here you can customize the date format for the date picker used by data entry fields. A full list of format options can be found here.
- Date Format for Date Picker: Customize the date format from the date picker used by data entry fields. A full list of format options is here. Tip: If you specify mm/dd/yy (I.e. 09/30/2020) or dd/mm/yy (i.e. 30/09/2020), any date input will be validated against those formats.
- Languages for Google Translate: Include a Google Translate option in your tree to automatically translate non-English foreign languages. Example: add fr,es,de to add French, Spanish, and German. You can add other 2 letter language codes to the list. The complete list of languages is here. Use * to support ALL language translations that Google offers.
Method 2: Export your Tree for Human Translation
Here’s how to translate your decision trees:
1. Export your decision tree (which creates a JSON file).
2. Use an online localization tool, (Like Sisulizer for example) to extract strings from the JSON files, and deliver them to a translator. Once translated, Sisulizer will make a new JSON file with the replacement strings.
3. Import the translated JSON file back into Zingtree. The Import option lets you overwrite an existing tree, or create a new tree.
One great feature within Sisulizer is that it automatically tracks text changes from updated versions of your decision trees; the translation software flags only those changes, so the translator can quickly locate and modify just the new changes.
Using location data variables to branch based on location/language:
1. Go to Settings > Data and click Collect location data variables.
2. Now you can create a logic node that will branch to the correct language tree you created based on Location or Language.