When a translation file is uploaded to an Elucidat Project or when a Variation is created with a translation file, you may see a message indicating that there are errors in your file that need to be addressed.
When one or more errors are present in the file, the message will show some additional information explaining the type of error that has occurred. Here is a full list of possible errors and what they mean:
| Message | Explanation | Solution |
|---|---|---|
| You tried to upload an invalid file type of: "file type" | A file was uploaded that was not a CSV or XLIFF. | Upload an accepted file type (.csv or .xlf) |
| Please use xlf or csv only | A file was uploaded that was not a CSV or XLIFF. | Upload an accepted file type (.csv or .xlf) |
| This file does not seem to be valid XLIFF 1.2 | The file that was uploaded is not an accepted XLIFF file type. | Upload a correct XLIFF file type (.xlf) |
| Unfortunately we only support XLIFF 1.2 | The XLIFF file that was uploaded is not a supported XLIFF version. | Upload an XLIFF (.xlf) in a supported version (XLIFF 1.2) |
| This file does not seem to be valid CSV | The file that was uploaded is not an accepted CSV type. | Re-export and upload a CSV in an accepted type (for example, CSV UTF-8) |
| This file is not from the current Project | The file that was uploaded was exported from a different Project than the one it is being uploaded to. | Either upload the file into the correct Project or, export a new file from the current Project, translate the file and upload it into the same Project. If you're not sure which Project the file is from, you can find guidance in our CSV and XLIFF overviews. |
| Invalid HTML "__text__" on "__line__" | An HTML error has been identified. The message will show the text with the error and which line it can be found in your file. | Resolve the HTML error in the file. See below for guidance on this. |
| Invalid XLIFF on "__line__" | An XLIFF value error has been identified on a specific line in the file. | Resolve the XLIFF value error in the file. You may need to contact your translation vendor for this. |
| Invalid XLIFF value "__value__" for key "__key__" | An XLIFF value error has been identified for a specific part (key). | Resolve the XLIFF value error in the file. You may need to contact your translation vendor for this. |
| Caution: You can choose to upload the file without addressing the errors, however we do strongly recommend that the errors are resolved before uploading it as incorrect HTML can lead to unexpected behaviour in your new translated course. |
Common HTML errors and how to address them
Here is an example of an alert indicating that there are two errors in a translation file:
These alerts indicate that there are HTML errors in the file. The sections below will explain how to resolve these errors.
Incomplete HTML tag
The first bullet point in the error message indicates there is an error on line 112 of the CSV file. If the CSV is opened in a spreadsheet, line 122 will refer to the row number.
In the example, the following line has been flagged with an error:
<p>Thank you for using <strong>Elucidat<strong>! We hope through
using our platform that you also share our company values which are:</p>
There are two HTML elements in this line:
- the paragraph element (<p>)
- and the strong element (<strong>)
HTML tags often come in pairs with an opening tag before the text to define where the HTML begins and a closing tag directly after it to define where it stops. A closing tag is indicated with a backslash (/) before the tag name. For example, </strong>.
An example of a correctly formatted tag pair would be:
<strong>Hello</strong>
In the example, the paragraph (<p>) element pairs are correctly formatted; there is one opening tag and one closing tag. But the word Elucidat has an incorrectly formatted strong element applied. The backslash (/) is missing from the closing tag making the strong element incomplete:
<strong>Elucidat<strong>
To resolve the error, you need to go back into your CSV and update the closing tag so that it is formatted correctly to:
<strong>Elucidat</strong>
The fixed complete example will look like this:
<p>Thank you for using <strong>Elucidat</strong>! We hope
through using our platform that you also share our company values which are:</p>
HTML character entities
The second bullet point in the error message indicates there is an error on line 114 of the CSV file uploaded. In the example, the text with the error is:
<p>Please press the continue button to continue to the next page &
<strong>learn</strong> more about our platform!</p>
The error has been flagged due to the presence of the ampersand (&) symbol.
In HTML, the ampersand symbol indicates the start of a code known an entity. These are necessary in order to represent special or otherwise reserved (those that have a specific function) characters in HTML.
In order to display the ampersand symbol, the character entity & must be used. Using & on its own will be interpreted as an incomplete character entity and flagged as an error. Some examples of characters that need to be represented as entities include the less than (<) and greater than (>) symbols which are represented as < and > respectively.
| Tip: When your translation file is exported, any HTML entities will already be formatted correctly in the source text so just ensure that they are not changed when adding translated text |
To resolve the error, you'll need to replace the ampersand with the correct entity (&) so that the text becomes:
<p>Please press the continue button to continue to the next page &
<strong>learn</strong> more about our platform!</p>