Under Community Review

Unicode characters are considered emojis and a font is applied to them that doesn't support the character

We have found that Trados Enterprise consideres some Unicode characters emojis and replaces the font with a font that doesn't support the Unicode character. This means that the character is not displayed properly after export.

Marco Mora
Parents

  • Specifically, the problem that we've encountered is that the source files we work with have Unicode characters such as Bangbang (Unicode character U+203C, https://www.compart.com/en/unicode/U+203C) which displays properly in the source document. However, when we translate the file and use all tags properly, the font gets replaced with "Segoe UI Emoji", which does not support the Unicode character Bangbang so it's displayed as a box. 

    The solution we're proposing is that instead of replacing the font around emojis as a default, to make it optional in the project/template settings. 

Comment

  • Specifically, the problem that we've encountered is that the source files we work with have Unicode characters such as Bangbang (Unicode character U+203C, https://www.compart.com/en/unicode/U+203C) which displays properly in the source document. However, when we translate the file and use all tags properly, the font gets replaced with "Segoe UI Emoji", which does not support the Unicode character Bangbang so it's displayed as a box. 

    The solution we're proposing is that instead of replacing the font around emojis as a default, to make it optional in the project/template settings. 

Children