Hi Anne Bühler 

Did you do a reset of your Trados settings (Workaround 2)? https://gateway.sdl.com/apex/communityknowledge?articleName=000001414

Kind regards,

Hi Elisa,

no I didn´t.

As I said, I only put the font for my language (german switzerland) back to "standard" instead of "arial", and everything is running well since then. That´s why I´m quite "shocked" that such a trivial problem leads to a total freezing of Trados.

Best regards,

Anne

Hi Elisa,

no I didn´t.

As I said, I only put the font for my language (german switzerland) back to "standard" instead of "arial", and everything is running well since then. That´s why I´m quite "shocked" that such a trivial problem leads to a total freezing of Trados.

Best regards,

Anne

Anne Bühler 

It's one of those "trivial" problems that is actually not so trivial at all and is actually quite complex under the surface.  Trados Studio recently underwent a significant update, including a complete overhaul of the Editor’s underlying technology to enhance font rendering, particularly for Unicode-compliant fonts.  While this update greatly improves clarity and compatibility, Trados Studio still allows any installed font to be used, including those that aren’t fully Unicode-compliant.  As a result, selecting a font like Arial, which lacks full Unicode support, can lead to a problem such as the one you’ve experienced.

Switching to the default font, as you’ve done, should address this.  For some flexibility with more comprehensive Unicode support, you could consider using fonts such as Arial Unicode MS (an extended version of Arial), Segoe UI, or Noto Sans, which offer broader character coverage and hopefully wouldn't cause a problem like this.

Hi Paul,

Thank you for taking the time to answer.

The problem may be not that trivial, but the solution is really very simple (and not these quoted workarounds solutions). As many users seem to encounter this problem, Trados could communicate it via a release note by buying the update, it would spare a lot of annoyment and stress.

Best regards,

Anne

Anne Bühler 

I appreciate your perspective on this issue.  Did you have a chance to search the knowledge base?  There are several articles that address the generic error message you mentioned.  I completely agree that this should be included in a release note, but in practice, I wonder how effective that would be.  Many users tend to overlook release notes, and the error message itself is often too vague to pinpoint a specific problem.

But I'm glad you managed to find the solution to help you continue working.

Hi Paul,

I haven´t search the knowledge base, I found this solution in Shosaku Takatani´ post.

I´m glad (and very relieved) too, thank you for the support!

Best regards,

Anne