Giant icons in SDL Trados Studio 2021

Question

Dear all, 
 Am I the only one who experiences giant segment status icons in Studio 2021? Everything else displays OK (i.e. like in previous versions). 
 I have patiently waited for a fix since I can revert to Studio 2019, but nothing changed despite several updates. 
 I do own a high DPI laptop that Studio notoriously struggles to supports. But since these icons render correctly in Studio 2019 and 2017, Studio 2021 should be able to do the same.

In version SR1 16.1.6.4276 
 In latest version SR1 16.1.8.4404

Philippe

Loredana Stoia · Answer

Hi, 
 Targeting to release by end of next week. 
 Thank you 
 Lori

Lydia Simplicio · Answer

Hello @ Philippe Noth 
 I have only seen such large icon issues reported once or twice before. 
 Ensuring both Studio & Windows (including all drivers) are on the latest stand has helped. 
 Also please ensure the Windows scaling is correctly set to 100% should also help. 
 We also offer the following app 
 https://appstore.sdl.com/language/app/change-scaling-behaviour/790/ 
 and other recommendations that could help here 
 https://gateway.sdl.com/apex/communityknowledge?articleName=000001872

Paul · Answer

Philippe Noth 
 Philippe Noth said: It seems that RWS and Steven never bothered to analyze seriously these scaling issues. To a complex and annoying issue, they always provide the same standards answers – recommendations that mostly do not work, see the Termbase discussion: 
 On some levels an incredibly ignorant reply, but I can see where you're coming from and you don't have any insight into what the development team is doing. I too would be really irritated by behaviour like this in a tool I use every day. 
 Steve and others helping out in here can only suggest what may help based on what they have seen. They are not developers. Your own investigations have already added a level of knowledge that could well be helpful to others as well. 
 The development team are working to improve the situation to the best of their ability. But it's a complex issue that is a work in progress. Each release gets a bit further and inevitably we break things from time to time that may affect some users (fortunately not too many have this problem you are facing). Studio is built at the moment using two technologies: WinForms and WPF. WPF is more open to supporting our ability to display better on all types of screens as it allows us to work with the Microsoft interfaces in a more controlled way. But since we have been effectively rewriting all the code to change from Winforms the move to WPF is not complete. 
 The two main challenges that that we are facing that prevent us from more easily switching completely in one big release to WPF are dependencies on 3rd party controls which require careful and significant effort to change. This means that some screens, or parts of them are still in Winforms. They are just wrapped in a WPF shell. 
 We definitely have analysed these problems, certainly a lot more than you would know, and we will continue to work on improving things as we go forward. I'll share your comments with the development team and see whether they can suggest anything you have not tried already, but hopefully as we go forward these problems will become a thing of the past anyway.

Bogdan Costisor · Answer

Philippe Noth 
 Hello, as a fellow developer I want to provide you some insight into the challenges we had with HiDPI. Firstly, we have the following requirements as input: we need to support various DPI & scaling ranges on multiple versions of Windows (7, 8, 8.1, and a multitude of sub versions of 10) for different monitor sizes (200% scaling on a narrow screen is not the same on a wide screen), multiple monitors with different DPI and different technologies (Trados uses WPF, WinForms and raw C++ for exactly the area you mentioned in the screenshot) 
 When we started working on this change we had to decide between the newest algorithms that Windows was automatically using or do it ourselves. If we were to allow MS to render Trados, what it would have done is render it at low resolution and upscale it. Their latest anti-aliasing algorithms are great, but they are only available on the latest WIndows 10 updates (v 1903). If we were to fully let Windows handle the scaling we would get blurry icons on some older version of Windows 10. 
 As a developer and user of paid software I do understand your disappointment, yet in spite of these current setbacks we still think it&rsquo;s better for us to handle all these rescalling than to be at the mercy of a new Windows update. 
 Regarding your mention that other software works perfectly, an example would be Microsoft Teams that has issues on different versions of Windows. 
 For more info please see the following link related to Windows scaling issues for high-DPI devices . 
 You can imagine the effort needed to fully test all these combinations. It would be of great help for us if you tell your OS version, Per Monitor scaling and Resolution, which one of these monitors is your primary and finally on which of these monitors you startup Trados.

Loredana Stoia · Answer

Hi Philippe Noth Stepan Konev , 
 Thank you very much for all the details provided regarding the issues, this will help us understand where the problem stands and be able to fix it faster. 
 We are tracking the item under : https://jira.sdl.com/browse/LG-30272 and it is currently planned to get out with Studio 2021 CU9 release (after Studio 2021 SR2 release). 
 However, if we manage to find the time necessary to fix this for an earlier release I will update this post with the changed release timeframe. 
 Thank you 
 Lori Stoia (Studio Product Owner)

Loredana Stoia · Answer

Hi Samuel, 
 The fix for the issue mentioned will be available with Studio 2021 SR2 release - which is due in about 3-4 weeks (beginning of October). 
 My suggestion would be to wait for that release and test afterwards as that would be a released version of Studio. 
 Thank you for your patience 
 Lori

Trados Studio > 1. Trados Studio

Giant icons in SDL Trados Studio 2021

Top Replies