Anna Jalmars 

This isn't an issue... just a setting.  Many translators prefer to translate without any formatting at all because it's not really relevant, and all formatting is controlled by tags.  A bit of an old article but probably still relevant:

https://multifarious.filkin.com/2012/09/10/working_with_tags/

Thanks Paul, exactly what your friend suggested above, and that's not the issue unfortunately. All tags and fonts should be displayed; originals is in times new roman, I'm not translating into a Slavic language and have never had this issue before. This is something more complex, it seems.'

Anna Jalmars 

ok... a couple of thoughts:

1. can you share a screenshot of the editor view?  You can mask the content, just don't obscure anything else
2. can you confirm what file you are opening?  So did you create the project and if you did what was the extension of your source file?

Of course! No, I did not create the project. When my project manager opens the exact same project in her Trados, the files are displayed in their original fonts, i.e. Times New Roman. I was sent a normal trados project, the same way I've been sent thousands of projects. Files are normal sdlxliff-files.

Anna Jalmars 

Now I am really baffled... What I see here is the same font on source and target side. So where is the problem? What a difference makes the view in TNR to what I see here? The font in your screenshot is perfectly readable, much better than the clumsy TNR.

Anna Jalmars 

Have you changed any of the defaults for displaying the fonts in the Editor?  Have you tried a reset just in case something is getting stuck?

Hi Paul,
Problem persists, I have not changed any settings. Copy-pasting what my PM sees in her view, and what I see in my view:

Anna Jalmars 

With your document open in Editor go to View and use "Reset window layout".

This said, I really fail to understand the problem. Your view with a non-serif font is much clearer and better readable than this clumsy view from your PM. Why is this so important to see the serifs? The font will not change anything in your translation, it has literally NO influence on it.

No, reset window layout doesn't change anything (I saw your reply above that you don't see this as a problem. I do, and that's why I'm trying to find a solution.)

Anna Jalmars 

Are you really sure the font used is Times New Romand and not any other Times or other serif font? 

Can you try to go to File -> Setup -> Manage user profiles and firs export your user profile. Then chose "Change user profile". You'll be asked to backup your current profile. Create a backup with a new name, not the one you used before. When you reach the step "Select User Profile", click "Browse", then go to C:\Program Files (x86)\Trados\Trados Studio\Studio18\UserProfiles and chose a profile from there. Should you be asked to overwrite any profile, do so. In next step reset window layout again.

Go to File -> Options -> Editor -> Font adaptation and press "Reset to defaults".

If all this does not help, I have no further ideas.

Anna Jalmars 

That screenshot helps I think.  Perhaps the only problem is your default font for the editor is not the same?  Select the language you are translating into and make sure the font is the one you wish to use.  Also make sure you have the same fonts as your colleague.  And finally what version of Studio is your colleague using compared to you?  There was a lot of work carried out on the editor in more recent versions to improve the clarity of the fonts and for most users the view you see would probably be preferable as it is far crisper than the one in your colleagues screenshot.  This isn't the font that is used for the final document, it's only the editor view.

Other than this I don't really know how to fix your problem.  Adding Bogdan Costisor in case he has any bright ideas :-)

 Paul Anna Jalmars Jerzy Czopik I've fixed a font adaptation issue with CU3. The algorithm is as follows:
1. If the file has a font saved as metadata then that font will try to be used (MS Word files usually have this font in metadata).

2. If the font doesn't work for some reasons (not installed in Windows, not acceptable for the language you have to use it) or the file has no font specified (think of txt files) then we use the font adaptation 

3. If the Graphics Engine (the same engine that MS Word uses) find issues with that font it will defer to another font or to our default font Segoe UI.

As you can see there are many reasons a font might not be applied. The biggest problem usually is that it won't work well with some symbols so it might force the engine to select a better one. The biggest change I ever saw was the usage of 10 different fonts in a single segment for an Asian Language. 

 Paul Anna Jalmars Jerzy Czopik I've fixed a font adaptation issue with CU3. The algorithm is as follows:
1. If the file has a font saved as metadata then that font will try to be used (MS Word files usually have this font in metadata).

2. If the font doesn't work for some reasons (not installed in Windows, not acceptable for the language you have to use it) or the file has no font specified (think of txt files) then we use the font adaptation 

3. If the Graphics Engine (the same engine that MS Word uses) find issues with that font it will defer to another font or to our default font Segoe UI.

As you can see there are many reasons a font might not be applied. The biggest problem usually is that it won't work well with some symbols so it might force the engine to select a better one. The biggest change I ever saw was the usage of 10 different fonts in a single segment for an Asian Language.