Corrupted fonts / glyphs not displayed in Studio 2017?

I recently migrated to a new PC upon which I am using SDL Trados Studio 2017 -14.0.5821.4, which I used without problems for several months before the migration in my pair, which is Japanese to English.

For some Word documents, not all, the text in the source displays without problems, but the target text has missing glyphs. These are displayed as little boxes which I believe are referred to as "tofu" by some. Here's an example. First, the text as it should display:



Now the corrupted text:

This seems to be something like the problem described in this question about font corruption in Studio 2014. However, I have already set the default font in Options → editor → font adaptation → custom language fonts to a Japanese font, as can be seen here:



So what could be the problem? It is noticeable that when I first copy the source to the target, all the text displays correctly, but if I start editing the text in the target segment, the boxes appear. The boxes also appear in the TM results window.

Any help appreciated.

Dan

Parents Reply
  • Thank you for the suggestion. I tried changing the font for English to Lucida Sans Unicode, which I assume would be able to handle most Japanese glyphs. Unfortunately, that seemed to make no difference.

    On your second "why not just change the way you work and you'll be fine" point, I routinely copy the source to the target because Japanese sentences tend to be significantly longer than English sentences for the same content and need to be broken up into multiple English sentences. Having the source in the target allows me to break up the original long sentence into sections and translate one at a time, with my translation in English underneath each Japanese section. When I'm done I delete the Japanese text from the target and confirm the segment.

    And of course, since tags cannot be handled transparently, I often copy the source into the target so that I know exactly where to put the text within the relevant tags.

    Although Studio is the only software showing this problem, given that you have confirmed that there is no problem on your system, and given that there doesn't seem to be a problem on the old system, I shall take another look at my language settings.

    Dan
Children