If you intend to use DeepL API as your machine translation (MT) service in your Transifex projects, it's crucial to be aware that the handling of special characters as <, > or & will differ from the handling of their HTML representation entities < > and & To guarantee precise translations, kindly take note of the following handling procedures.
Special characters unescaped in the source string
If the special characters in the source string are unescaped, the translations made using DeepL API MT will contain these special characters unescaped as well. For example:
Source string:
Number of users is > 1,000.
Translation:
The number of users is > 1,000.
Special characters represented in their HTML entities in the source string
If a source string contains HTML entities to represent special characters, the translations made using DeepL API MT will also present special characters represented in their HTML entities.
Source string:
The number of users is > 1,000.
Translation:
The number of users is > 1,000.
Source string containing unescaped special characters and also special characters represented in their HTML entities
If a source string contains special characters in both, their HTML representations and unescaped, the translations made using DeepL API MT will have all the special characters represented by their HTML entities. For example:
Source string:
The number of users is > 1,000 and < 10,000
Translation:
The number of users is > 1,000 and < 10,000
💡Tip
Looking for more help? Get support from our Transifex Community Forum!
Find answers or post to get help from Transifex Support and our Community.