Ensure your batch translation file meets all formatting requirements to be imported successfully.
Your batch translation file must be created from the translations source file exported from the application that contains system data required for successful import. Ensure your batch translation file meets all the formatting requirements covered below.
Batch translatable columns
You can input translations for each language's content into the corresponding locale column that appear in the translations source file. However, you can only translate localizable content such as text-based survey elements.
Localizable elements:
- Question and answer text
- Alt text for question and answer images
- Rows and columns text for grid questions
- Categories and items text
- End survey messages and redirect URL
Non-localizable elements:
- The images in Highlighter and Image questions
- Number responses
- Question names and properties
Text formatting using HTML tags
Rich-text formatting can be imported through batch translations using accepted HTML tags. Any formatting done using accepted HTML tags can be carried forward through the import. However, unsupported or malformed HTML tags will not be rendered successfully, so the content will appear as entered without formatting.
The following table describes HTML tags that are accepted and where they are supported:
| Accepted HTML tags | Question Text | Instruction Text | End Survey Message | Answer | Row | Column | Category | Item |
|---|---|---|---|---|---|---|---|---|
paragraph:
<p></p> or
<p class="vci_small"></p>
|
|
|
|
|||||
bold:
<b></b>
|
|
|
|
|
|
|
|
|
italic:
<i></i>
|
|
|
|
|
|
|
|
|
underlined:
<u></u>
|
|
|
|
|
|
|
|
|
header 1:
<h1></h1>
|
|
|
|
|||||
header 2:
<h2></h2>
|
|
|
|
|||||
line break:
<br>
|
|
|
|
|
|
|
|
|
unordered list:
<ul></ul>
|
|
|
|
|||||
list item:
<li></li>
|
|
|
|
|||||
link:
<a
href="http://www.example.com"
target="_blank"></a>
|
|
|
|
|
|
|
|
|
Example: Importing bold text using the <b> tag
Batch translation file:
Survey authoring view after import:
Example: Importing malformed HTML tags
Batch translation file:
Survey authoring view after import:
Pipes
Once a pipe has been authored and exported to the translation source file, it can be imported through batch translations.
Example: Piping in a response from a previous question in the survey
Batch translation file:
Survey authoring view after import:
Blank cells
You can leave cells blank in the batch translations file and the import will still be successful; blank cells will be ignored, leaving existing content as is.
Example: Leaving zh-HK cells blank
Batch translation file:
Survey authoring view after import:
Hidden and non-editable data
Do not make changes to hidden and non-editable data in the translations source file, otherwise the import may fail. Protected view is automatically enabled in the file to keep the necessary data hidden and locked. However, the data can be made visible and editable when protected view is disabled.
Do not change the values in the data below:
| Column/Worksheet | Description |
|---|---|
| ID | Hidden column of system generated question IDs that map each row in the file to each question in the survey. |
| PropertyName | Hidden column of translatable properties. |
| Pipe mappings | Hidden worksheet of pipe mappings. |
| Page Name | Non-editable column of page numbers in the order displayed in the survey. |
| Question Name | Non-editable column of the survey elements as named in the survey. |
| Type | Non-editable column of the types of survey objects. |
| Default | Non-editable column of the survey contents in the default survey locale. |