Problems with SDL Trados Studio on a QHD Screen? If you are working on a ultra high-resolution screen like Yoga 2 Pro, chances are your SDL Trados Studio (2011, 2014) does not scale properly and you end up with an ugly user interface like the one below:
A Workaround for SDL Trados Studio on a QHD Screen
This problem is not particular to Trados Studio. Any application that is not High DPI aware (ie Adobe Fireworks) will suffer from the same scaling issue. A quick fix is to change your screen resolution to a typical HD setting (ie 1920×1080) but that’s not an optimal solution as you will lose your beautiful QHD output for other applications.
Telling Windows to Scale Trados at lower DPI
Step 1: First you will need to edit your registry to tell Windows to look for an external manifest file when an application launches.
WARNING: Even though steps are very simple, editing the registry is dangerous and may cause your computer to malfunction. Continue at your own risk.
- Press Windows Button + R, type “regedit”, and then click OK.
- Navigate to the following registry subkey:
- HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > SideBySide
- Right-click, select NEW > DWORD (32 bit) Value
- Type PreferExternalManifest, and press ENTER.
- Right-click PreferExternalManifest, and then click Modify.
- Enter Value Data 1 and select Decimal.
- Click OK. Exit Registry Editor.
Step 2: Create and place the external manifest file in to SDL Trados Studio folder under Program Files
- Download the manifest file – SDLTradosStudio.exe.manifest (this is a simple text file)
- Drop the file into the SDL Trados Studio installation folder. If you used the defaults, it should be at C:\Program Files (x86)\SDL\SDL Trados Studio\Studio3.
Make sure the file is named as SDLTradosStudio.exe.manifest as otherwise Windows will not recognize it.
That’s all. Go ahead and launch your Studio and it should scale properly. It will not look as crisp and sharp as the applications that support QHD, but it will be in much better shape than before.
For more information about this workaround, see this Microsoft knowledge base entry.
I discovered this solution while I was browsing for a similar solution for Adobe Fireworks. Credit goes to original author.