Studio slow-down with certain fonts


The segments switching in the first file is definitely smoother than the second. With the second file, a noticeable lag/glitch can be seen. There is also much larger text input lag, making the use of the software an unpleasant (and certainly not $700-worth) experience.

File size is about the same, project file storage location is the same. It clearly seems to be an optimization issue. My device is Surface Pro 2017, a Windows tablet with not-so-efficient Intel GPU, but do I really need a top-end GeForce to display FONTS smoothly?

I've seen this happen many, many times, and haven't spotted a trend so far as to which fonts exactly does Trados "prefer" for smoother operation.

With the "right font" (feeling like an idiot just typing this) the software runs very fast, switching the segments and searching the TM without any perceptible lag (quicker than on the video, which obviously has some inherent lag in it), so please don't tell me it's my inferior hardware.

The default language font setting (or something) in Studio only changes the font in the Translation Results window. Is there a way to fix the main translation text font too? Maybe this way I could achieve butter-smooth operation every day, with every project.

If not, what might be the problem? Has any of you experienced this?

Parents Reply Children

    File -> Options -> Editor -> Formatting Display Options -> Show all tags but do not show formatting

    That will use the default Studio font for whatever your target language is.  All explained in the videos.

  • Just tried the option, and I think it got even laggier than before! Also, I don't see how an agglomerate of tiny tag marks is less distracting than a neat, tagless text with visually applied bolds, colored text, etc - but maybe it's just me. Maybe some people like it the crude way.
  • Hi , then I don't really have a good answer for you. People I know who use the plain text mode do so for the consistency and speed of working. I think the wysiwyg mode is great for reviewing, but not for translating. The tags are always there and selecting them based on formatting is far more difficult (in my opinion anyway) than it is as visible tags. I guess it's a case of horses for courses!
  • Yeah, horses for courses.

    Either way, since you have the "connections" maybe you could submit/inquire about this issue to the developers? Because it's clearly a GUI optimization fault which wasn't there in Studio 2011 (on the same PC). And it's not only me who experienced this (as proven before). Maybe it's a recent .NET issue? Seems like something being wrong "at the core" of the software.
  • Here's a visual example of Studio magically speeding up after changing font size: (the issue described in the previously posted ProZ topic)

    One could say that it's related to my hardware performance, but how can hardware perform BETTER when having to display MORE characters on the screen than before? To me this looks like a problem with Studio optimization and one that requires the designers' attention for the upcoming SP.
  • ok

    Let's try this then.

    1. You tell us what fonts you are using so we can reproduce it
    2. You preferably give us the same file you are using (as there may be other things at play)

    Showing some silient videos is not enough for us to explain anything other than guessing where the problem might be coming from. We're perfectly willing to look at this and see why it's happenning... and it could even be related to your own specific hardware... but help us to achieve what you are trying to show and we can see what can be addressed.
  • I'm currently testing with Arial Narrow with the "show tags but no formatting" setting to see if there is improvement, I'll keep you posted.

    I know the videos aren't enough to explain anything, but they are - hopefully - enough to prove I'm not bullshitting you and for the issue to be potentially treated seriously by your team.

    This might be hardware-related indeed, but Microsoft Surface Pro (2017, i5) is not a product from Mars, so hopefully it is/will be "supported". It runs on regular Windows 10.

  • Just made a test that proves definitely a MASSIVE lag difference between Arial Narrow and Arial with the project that I'm currently doing (just a regular original .docx contract, text only). I changed the fonts several times and there is 100% reproducibility - with Arial there is a massive lag when switching b/n segments, which pretty much goes away after switching to Arial Narrow. With Arial it feels like I'm on a 1990's laptop GPU.

    Sure, my Surface only has a modest Intel GPU, but... it should handle TEXT, right?

    Although, to be honest, I recently realized that there is a very similar phenomenon with MemoQ on this PC - when I decrease the font size to, say, 13 from 18 the segment switching and text input lag reduces immediately. So it might be something wrong with my PC (yet another silly issue with this godforesaken machine), but what exactly?! This you're probably not going to tell me, which I understand.

    Nothing of this sort happens in MS Word or MS Edge, so it's not like my laptop has a problem with large fonts in general - it's just certain programming environments. But then again: MemoQ and Trados are quite a distance apart in these terms (programming platforms), aren't they?

    Do try the font switching yourself in the meantime. I can't provide my current test file due to NDA.

  • Just tested with MemoQ and it's exactly the same... So it's my retarded Surface environment after all. Probably GPU misoptimization.

    Sorry for the hassle.