SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
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?
Hi Paul, I don't use any particular fonts, just the default settings. The font changes depending on the file. I have the font size adaptation setting enabled, and that's all. I'll try the trick you linked when I have some past-time for troubleshooting, thanks. I also had the following issue: tam.proz.com/.../259903-slowing_down_with_large_font_adaptation.html (note that the original post is not mine)
PS. The video obviously doesn't fully present the severity of the issue, but the slowdown is evident at a glance in "real world". Also, text input lag increases A LOT.
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.
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.