Scaling for 4k in 2022

I just upgraded from Trados Studio 2021 Freelance Plus to 2022 Freelance Plus. Unfortunately, 2022 STILL doesn't support 4k resolution (how is this possible in 2022?), and the third-party "Change Scaling Behaviour" app in the appstore that fixed the problem has not been updated for 2022. Does anyone know a solution for this?

emoji
Parents
  • Well, I can confirm that this problem STILL persists, even though it is past the middle of 2023. This is a joke. I purchased a 4k screen computer and now I cannot even work properly in Trados. That is not to mention that it STILL is a 32-bit system, that does not support anything north of 3 GB of RAM. Which is a joke, since Trados crashes on my computer regularly.

    This a question to the developers: Have you guys heard of modern technology or do you just release new versions without even addressing the elephant in the room that probably almost everybody has to or will have to deal with in the near future?

    emoji
  • I purchased a 4k screen computer and now I cannot even work properly in Trados.

    Why? You can magnify the font in the Editor to whatever size you want. I have a 13" laptop with a resolution of 3840×2400 plus an extra 13" screen with 3840×2160 when on the road and can work with Studio without bigger problems. Of course I do also miss some options to magnify other parts in the editor, but still Studio is workable on such systems.

    As per 32 bit I would advice to read comments by I work a lot with Studio and the crashes are extremely rare.

    emoji
  • Jerzy, this has nothing to do with the size of the Editor font. Read this thread from the top, and look at the screenshot. This is a big glaring problem, and an embarrassment for a program with "2022" in the title. I am still using the 2021 version for this reason.

    emoji
  • Of course, you can magnify and scale certain things, but Studio does not seem to support such things out of the box. As an experienced linguist and a technology user, I can manually configure such things, no problem (or not much of a problem, at least). BUT, if my employees have the same issue, I need to devote time to configure each system manually. And why should I? Can't Trados Studio simply detect the screen's resolution and scale accordingly? For a 4k screen, the out-of-the-box experience is terrible—icons are either tiny or scaled and blurry (without experimenting with certain Windows scaling options). Also, I do have a system with two displays, each 4K, but also each with a different resolution (Asus ZenBook Duo with dual screens)—working with Trados Studio on this laptop began as a nightmare before I figured out what to do and what not to do (no switching screens with Studio open etc.).
    As per 32 bit—perhaps crashes are extremely rare. In Paul's case. In mine, not so much. My Trados Studio 2022 Professional tends to throw error messages (various kinds) whenever too many projects are open or when the open project is too large. Then it just shuts down - sometimes a few times per day. Or when I try to create a new project for my team while simultaneously working on a translation assignment on my own - immediate crash. No matter if I reinstall Studio, get a clean Windows install and a new Studio install - the same thing happens quickly with more advanced projects and ESPECIALLY multitasking. Most error messages do mention the "out of memory" category of errors. And I have 64GB of RAM on my end... This has been the case for the past few versions of Studio, on various computers.

    This software has bugs. Lots of them, and most of them are copied and pasted over from legacy versions into the new ones, without even solving them. 64-bits would solve a lot of them, since this is an architecture used for close to 20 years now. In IT this is an eternity.  

    Nothing can really change my mind about the disadvantages of Studio at this point—I have been a loyal user since Studio 2011 and GS14, so I know pretty well that the problems I mentioned existed even then. Disappointed

    emoji
  •  

    Check your graphics driver or other settings. Here is how Studio looks like on my laptop with over 4K resolution:

    Screenshot of Trados Studio interface on a laptop with over 4K resolution, showing no visible errors or warnings.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 11:31 AM (GMT 0) on 29 Feb 2024]
Reply Children
  • I think it's interesting that you consider that resolution to be normal or acceptable Laughing

    Here's what Studio 2021 looks like with the "Change Scaling Behaviour" add-in:

    Trados Studio 2021 interface with 'Change Scaling Behaviour' add-in, showing clear and properly scaled text and icons.

    Screenshot of Trados Studio's editor with a warning message 'No open translation memory', indicating a missing translation database.

    This is what out-of-the-box 4k scaling look like, in EVERY other program I've ever encountered EXCEPT Trados Studio. "Change Scaling Behaviour" has not yet been updated for 2022, and Trados itself has NEVER fixed this issue in its own code. Rather ridiculous, considering that 4k has been standard for nearly 10 years and that seemingly every other software company on earth has managed to cope.

    So Mateusz is right to find this unacceptable. There are a LOT of bugs that just get carried forward from version to version and never get fixed, like the inability to count words properly after merging or splitting segments. Or the general instability of the program that Mateusz refers to: I have the very latest/fastest laptop on the market with maximum RAM, and the program still crashes unexpectedly for no apparent reason. (Periodically, the common shortcut CTRL+C triggers a crash!)

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 11:32 AM (GMT 0) on 29 Feb 2024]
  • That Ctrl+C has actually just crashed my computer! I agree with everything you wrote. Even an Intel i9, 64GB RAM and a quick SSD don't help - Trados is always slow and eager to crash unexpectedly. Three times today (so far) - with random errors. The latest was an error writing to a TM (a GS one at that). After opening the software again, however, the segment turned out to be correctly saved. So Trados crashed without a good reason.

    I have some experience in software development (as a project lead), so I know what this could mean. It could mean that (and most probably does) that you are aware of this problem, but you decided not to address it. And not because it is rare, but rather because it lies deep within the core of your system and correcting this issue could possibly shatter the whole software, and you just cannot afford that (either you would be working on new patches and 2023 edition, or repairing the 2022). So you rely on third-party software to address such issues or just ignore them altogether, since the software otherwise works. And I really, REALLY, know this is standard practice for many companies—even the largest ones (I really, REALLY know that from personal experience). And it is a shame, since this is an industry-standard software, priced at a high level, with dozens of thousands of licenses sold globally, so one would surmise you could afford to finally make the switch to 64 bits and make the system more stable at least...

    emoji
  •  

    This is how Outlook and Word look like on the same machine:

    Screenshot of Microsoft Outlook with an empty inbox and a message stating 'Es wurden keine Elemente gefunden, die den Suchkriterien entsprechen.'

    Screenshot of Microsoft Word with a blank document and a cursor at the beginning of the page.

    Outlook is even worse than Studio, as the possibilities to adapt fonts are really limited...

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 11:32 AM (GMT 0) on 29 Feb 2024]
  •  

    Please check how current your Studio is. From what I remember there was a bug with shortcuts way ago...

    emoji
  • Thank you but this is not a shortcut issue. I use this shortcut all day long in Studio, but just now - it crashed while i was using this exact shortcut. Studio just seems so ... wobbly lately. Unstable. I never seem to know what might set it off - as if it had moods of its own and crashed just for fun "because it can". Sometimes it feels that way :).

    Also, currently I am using the newly-installed SR1. It is mere hours old :).

    emoji