1. Trados Studio - Recent Threads

AI Assistant: Can I Assign a Keyboard Shortcut to “Apply Selected AI Translation”?

Meguru Tokiwa — Sun, 16 Aug 2026 07:56:53 GMT

Hi,
I’ve just started using AI Assistant, and I find it very useful!

I would like to use AI Assistant with keyboard shortcuts. Is there a way to assign a shortcut key to the Apply Selected AI Translation button?

On the Keyboard Shortcuts settings page, I found the AI Assistant action and assigned a shortcut key to it. However, this action only moves the focus to the AI Assistant pane; it does not apply the selected translation.

Is there an action I can use to apply the selected AI translation?

Thanks.

Trados Studio 2024: All XML source and target text displayed in bold in Editor

Marta Guerrero — Fri, 14 Aug 2026 15:53:56 GMT

Hi everyone,

I see all text in the Trados Studio 2024 Editor displayed in bold. All source and target text appears in bold, except for the protocol title.

For context:

The project was created from an XML file exported from Storyblok. I can't modify or clean up the XML before exporting it.
The XML itself does not contain any <b>, <strong>, or other bold formatting tags.
The issue affects all segments except the title. I also notice that the segments are classified as CDA/CDATA Section, which might be related?
Some formatting options in the Editor are greyed out, while others do not seem to have any effect.
In Options > Editor > Font Adaptation, both English and Spanish are set to (default).
Disabling Adapt font sizes makes the text smaller, but it still appears bold.
Previous projects did not have this issue, although this has been happening for some time now.

If anyone has encountered this issue or knows how to resolve it, I'd be grateful for any suggestions.

Thanks in advance!

Marta

PS- Trados Studio 2024 SR1 - 18.1.4.6694

Trados 2022 Studio SR2 has discontinued to convert PDF files into translatable format.

Eberhard Nietzer — Thu, 13 Aug 2026 14:03:16 GMT

My Trados software has worked fine with PDF files for a long time.

I have scanned several documents with two different scanners and saved them as searchable PDF files.

When I open the PDF file in Finereader 15, I can edit and copy text, so the PDF has real text, not only images.

When I add the searchable PDF to my Trados project, Trados performs the batch tasks fully without any error messages.
However, when I open the PDF with Trados, the result looks like this:

Words:

How can I make Trados 2022 convert PDF files into translatable format again?

Autocorrect does not take effect in Review mode

Walter Blaser — Wed, 12 Aug 2026 11:37:01 GMT

The Autocorrect function under 'Options - AutoCorrect" seems to work only when one is in Translation mode.

If one reviews a document, these options do not apply.

This is very unappropriate, because it raises situations which are very difficult to overcome.
One example: you are revising a document and the translator has inserted straight quotes instead of curly ones. You want to correct this, but you cannot unless you know the keyboard combination for the curly quote because your typing always inserts a straight quote.
We have this problem in Trados Team where we get translated documents with straight quotes and cannot correct them. We had to implement QA regex rules to make sure that translators get their task returned as long as their text contains straight quotes.

The same is true for all other autocorrected characters.

Is this by design or a bug?

It seems that this problem exist since quite a while, see this post:
(70) Straight apostrophe when Tracks Changes is activated. I need curvy one. - 1. Trados Studio - Trados Studio - RWS Community

How can I translate Word fields (internal hyperlinks) in Studio?

Sabine Freyling — Wed, 12 Aug 2026 08:59:18 GMT

I have text fields in a Word doc and the answer provided here: How can I translate Word fields (internal hyperlinks) in Studio? - 1. Trados Studio - Trados Studio - RWS Community does not work. Is there any other way to deal with this issue?

Thanks,

Sabine

Saving the target text on Trados 2022

Taoufik Allah Afkinich — Tue, 11 Aug 2026 22:00:13 GMT

I want to save the target text in Word Format on Trados 2022. I have a freelance subscription to this product. However, the recording does not get through. Instead, I get this error message: "Échec de l'enregistrement du contenu cible : L'illustration a été déplacée entre les paragraphes". Your help will be much appreciated.

PANIC STATE : Erratic display after Windows 11 updates

Claude Brindamour — Tue, 11 Aug 2026 15:08:32 GMT

This problem is unsolved and could compromise my work.
Strange behaviours of Trados Studio 2024 occurs since recent windows updates
(image blinking repeatedly, program display on 2 screens, program is "zooming in and out" or flashing).
Here's what I tried and thank you for your help.

Installed last Intel driver (32.0.101.7085)
Intel update OK
Windows Update OK
Firefox : unticked material acceleration
Refresh Firefox
unticked unnecessary Add-Ons
--------------------------
My computer : Intel Core i7 12700
Alder Lake
12th generation Intel Core i7-12700
--------------------------
Intel Graphics Software & Drivers Installer
New ASUS screen, verify the resolution is the same on both screen
--------------------------
Trados Studio 2024 SR1 - 18.1.4.6694
Reset Window Layout
High DPI settings (modify the behaviour)
Rename Local parameters files to provoke the creations of new ones (AppData\Roaming\Trados Studio)

After many attempts (even buying another monitor, TRIED going back to previous update) the problem is still there.

Select Match shortcuts do not work in Studio 2026

Sandor Juhasz — Mon, 10 Aug 2026 06:40:16 GMT

Now and again, the Select Match shortcuts (Ctrl + number) go wrong in Studio 2026. Now I cannot use them, but they worked fine before. Please, help.

Language Weaver

Aurélie Machut — Fri, 07 Aug 2026 17:00:51 GMT

Hello,

Starting with Trados 2026... Can you tell me what kind of file is expected to enhance pre/post translation?

Thanks

Aurélie

Trados Studio 2026 bug: Segment status changes to "Not Translated" when changing comment severity from "Info" to "Error"

Sabina Fata — Fri, 07 Aug 2026 15:07:14 GMT

Hi,

making extensive use of comments in Trados Studio 2026 I noticed that when I change the severity level of a comment from "Info" to "Error", the relevant segment changes to the status "Not Translated" even though the segment had been confirmed previously.

Please fix this.

BTW: I just LOVE the new comment window and the colours! Thank you for the great work.

A wonderful weekend to everybody!

Regards,

Sabina

Studio cannot use SDLTB, MultiTerm cannot use TTB: How is this a workable transition?

Michael Schroeder — Fri, 07 Aug 2026 06:33:09 GMT

I would like to start a broader discussion about the current state of local terminology management in Trados Studio 2026.

To be clear, I am not opposed to the new TTB format itself. I understand that replacing the legacy SDLTB format may be necessary to provide a more modern foundation for terminology in Studio.

My problem is that RWS has made the new format mandatory before delivering a terminology-management workflow capable of replacing the previous one.

The current situation, as I understand and have experienced it, is as follows:

Existing SDLTB termbases can be converted to the new TTB format.
Trados Studio 2026 no longer supports SDLTB termbases.
MultiTerm Desktop 2026 does not support the new TTB format.
The new Termbases view in Studio provides certain administrative functions, such as creating termbases, configuring settings, and importing or exporting data.
However, it does not provide a proper environment for browsing, editing, and maintaining terminology entries.
Routine entry work therefore has to be performed in the small Termbase Viewer within the Editor, which means opening a translation project simply to manage terminology.
TTB export appears to be limited to exporting the complete termbase. There is no equivalent of the filtered export workflows available in MultiTerm.

That last point has a major practical impact on our terminology processes.

We regularly need to export selected subsets of a termbase, for example:

newly created terminology;
entries awaiting review or approval;
approved entries;
terminology from a particular subject area;
entries selected for exchange with a particular group or system.

A full XML export is useful for backup and interchange, but it is not a replacement for filtered, workflow-oriented exports.

In theory, I suppose I could export the complete TTB database as XML, create a new SDLTB termbase in MultiTerm using the appropriate termbase definition, import the XML, and then perform the filtered export from there.

But are users seriously expected to reconstruct and maintain an SDLTB version of their terminology whenever they need functionality that was already available before upgrading?

This also creates obvious risks:

duplicate termbases;
uncertainty about which database is authoritative;
synchronization problems;
unnecessary conversion and import work;
possible loss or alteration of data during repeated round trips.

Incremental development is understandable, but this is not a feature that can safely be replaced in tiny, disconnected steps when the old workflow is removed at the same time.

A responsible transition could have taken several forms:

Studio 2026 could have continued supporting both SDLTB and TTB until the new workflow was complete.
MultiTerm 2026 could have supported TTB during the transition.
TTB could have remained optional until the essential terminology-management functions were available in Studio.
A reliable bidirectional conversion workflow between TTB and SDLTB could have been provided.

Instead, Studio cannot use the format supported by MultiTerm, while MultiTerm cannot use the format required by Studio. At the same time, Studio does not yet provide the terminology-management capabilities that MultiTerm previously supplied.

From the perspective of someone who actively manages terminology rather than only looking up terms while translating, the storage and recognition layer may be ready, but the terminology-management workflow is not.

I therefore have two questions for RWS:

What is the intended workflow in Trados Studio 2026 for professional terminology management, particularly entry maintenance, filtering, review, approval, and selective export?
Why was SDLTB support removed before either Studio or MultiTerm could provide a complete working environment for the new TTB format?

I would also be interested to hear how other terminology managers are handling this transition. Are you maintaining parallel SDLTB and TTB termbases, rebuilding SDLTB databases from XML exports, remaining on Studio 2024, or using another workaround?

Error: Cannot validate SDL plug-in

Antonia Trakkidou — Wed, 05 Aug 2026 13:31:43 GMT

Hello. I just activated Studio 2019 on my new laptop. When I try to open it, I get the following error: SDLErrorDetails time="05/08/2026 14:18:43">
<ErrorMessage>Cannot validate SDL plug-in: Sdl.TranslationStudio.Packaging.PackagingService, Sdl.Translation

Can anyone help me please?

Trados Studio 2019 SR2 15.2.8.3007

Messages pane always activated in Studio 2026

Sandor Juhasz — Wed, 05 Aug 2026 07:58:04 GMT

In Studio 2026, the Messages pane is always activated when a new message is created after segment confirmation, and the Translation Results must be activated again and again. Reset Window Layout does not help.

Error "Failed to create temporary folder"

Pierre-Olivier Vilain — Tue, 04 Aug 2026 07:33:20 GMT

Hello,

I am experiencing some problem with Studio 2021 since yesterday.

When I try to open my current translation project, I get the followinf SDLUpdateClient error message: "Failed to create temporary folder: C:\\Windows\TEMP\ir_tu2_temp_0"

Could you please help me to solve this issue?

New idea: preview pane for the Comments window

Michael Beijer — Sun, 02 Aug 2026 19:45:14 GMT

I've just posted an idea on the RWS Ideas and thought I'd flag it here in case others run into the same thing:

"Comments window: show the full text of the selected comment in a preview pane"

In the Comments window, the Comment column is too narrow to actually read anything – with 45 comments in a file, all I see is the first word or two of each one, so the only way to find out what a comment says is to click through to every segment in turn. The idea asks for a resizable preview pane at the bottom of the window that shows the full text of whichever comment is selected, updating as you arrow through the list.

If that would be useful to you too, please give it a vote – thanks!

Michael

Error when using the Retrofit function

Mohammed Abdul Waheed — Sun, 02 Aug 2026 07:43:23 GMT

I have a large word file (+50k words) that I translated a few months ago. Today I received a revised Word document from the client. I wanted to use the Retrofit function to capture the changes made by the client but when the exercise is completed, I get an error message "cannot access a closed file". How do I resolve this?

Bug Report: Studio 2026 Editor – Found Regex Matches Not Visualized (No Highlight)

Sameh Elsharkawy — Fri, 31 Jul 2026 22:38:45 GMT

Submitter: [Sameh Ragab] Date: [1 August 2026] Product: Trados Studio 2026

Issue Summary

When performing a search in the Editor view using the "Regular Expressions" search mode, the application correctly identifies the segment containing the match but fails to visually highlight the specific text string within that segment that matches the pattern. This makes it extremely difficult to locate the match within long or complex segments. Normal "Find" operations (plaintext searches) do not have this issue.

Steps to Reproduce

Open any document for translation in the Studio 2026 Editor view.
Ensure the document has text appropriate for the test Regex, for example, a segment containing "(km)" or "(mile)".
Press Ctrl + F to open the "Find and Replace" window (or pane).
In the "Find what" field, enter the following valid Regex pattern for finding English letters or numbers in brackets: \([a-zA-Z0-9]+\)
Change the search type to Regular Expressions (via the dropdown menu or checkbox).
Click Find Next.

Expected Behavior

The Editor view should navigate to the next segment containing a match. Crucially, the specific string that matches the pattern (e.g., just the characters "(km)") within that segment should be clearly highlighted, typically with a yellow background, to allow immediate visual identification within the context.

Actual Behavior

The Editor view successfully navigates to the segment containing a match (the segment becomes active or is shown on screen). However, the exact matching text is not highlighted at all. The user is left to manually scan the entire segment text to determine where the match is located.

Business Impact

This defect significantly degrades productivity and usability. The purpose of a search tool is immediate location. Without visual identification of the matching string, users lose valuable time manually searching long or complex segments. This increases cognitive load and can lead to overlooking critical details that the search was intended to prevent, which is exactly why this feature is critical in professional translation workflows.

Additional Notes

This issue appears to be specific to the visual rendering in the Editor view when Regex is engaged. The search engine function is working (as it correctly identifies the segment), but the visual "Found" status for the specific text is not being reflected in the UI.

I hope this can be fixed soon.

Thanks a lot.

Sameh Ragab

Trados Studio 2024 – Repeated Out-of-Memory Crashes When Saving an IDML Project

Sameh Elsharkawy — Fri, 31 Jul 2026 17:09:15 GMT

Subject:

Dear Trados Support Team,

I am writing to report a recurring stability issue in Trados Studio 2024 while working on a standard IDML project containing approximately 58,000 words.

Studio crashes intermittently, particularly during saving, and displays errors such as:

System.OutOfMemoryException
“The memory could not be read”
“bad_module_info has stopped working”

The SDL error report indicates that the failure occurs during the process of writing the SDLXLIFF file, specifically while escaping XML content and embedding or linking the original dependency file. The relevant stack trace includes:

XmlEscape
WriteZippedFile
EmbedDependencyFile
WriteSdlXliff
SaveBilingualImpl

The affected environment is:

Trados Studio 2024, version 18.1.4.6694
Windows 10 Pro
Approximately 64 GB of installed physical memory

The error log confirms that Studio throws a System.OutOfMemoryException during the SDLXLIFF save operation rather than during translation or TM lookup.

I appreciate that Trados Studio 2026 is now available and that its 64-bit architecture should address many memory-related limitations. I already have Studio 2026 myself. However, this does not eliminate the need to investigate and, where technically possible, correct the problem in Studio 2024.

Many professional users may continue relying on Studio 2024 for valid operational, compatibility, licensing or client-related reasons. uat.community.rws.com/.../sdlerror_2D00_2026731_2D00_19h18m49s.sdlerror.xmlA file of this size should not cause Studio 2024 to terminate repeatedly without allowing the user to save their work reliably.

I would therefore appreciate it if your technical team could:

Confirm whether this is a known defect in Studio 2024.
Advise whether a cumulative update, hotfix or practical workaround is available.
Consider correcting the issue in a future Studio 2024 maintenance update, particularly the memory handling involved in writing SDLXLIFF files and embedding large IDML dependencies.
Ensure that, where a memory limit cannot be avoided, Studio fails gracefully and provides a clear warning rather than terminating unexpectedly and potentially placing the user’s work at risk.

I am attaching the SDL error report and screenshots of the Windows error messages for your investigation. The report identifies the crash as occurring within the bilingual-file save process.

Thank you for looking into this matter. I would be grateful if the case could be escalated to the relevant Studio development or file-type engineering team, as this appears to be a product-stability issue rather than a problem with the available hardware.

Kind regards,
Sameh Ragab

프로그램 동작 에러

Hee Ku Kang — Fri, 31 Jul 2026 08:12:00 GMT

당신의 답변 내용입니다 [

Trados Studio 2019의 작동 문제로 불편을 겪고 계신 점 안타깝게 생각합니다. 문제를 해결하기 위해 아래 단계를 따라 진행해 보시기 바랍니다:

### Step 1: Windows 업데이트 확인

Windows 검색창에 **"Windows 업데이트"**를 입력하고 **"업데이트 확인"**을 선택합니다.
새로 열린 창에서 **"업데이트 확인"** 버튼을 클릭합니다.
사용 가능한 모든 업데이트를 다운로드하고 설치합니다.
컴퓨터를 재시작한 후 Trados Studio 2019를 실행하여 문제가 해결되었는지 확인합니다.

### Step 2: Trados Studio 설치 복구

**제어판** > **프로그램 및 기능**으로 이동합니다.
Trados Studio 2019를 찾아 선택한 후 **"수정"** 또는 **"복구"** 옵션을 클릭합니다.
복구 프로세스가 완료될 때까지 기다린 후 프로그램을 다시 실행해 보세요.

### Step 3: Trados FreshStart 사용

Trados Studio의 설정 파일이 손상되었]

위에서 답변해준 것 중, '### Step 3: Trados FreshStart 사용'의 답변 내용이 표시되지 않았습니다. '### Step 3: Trados FreshStart 사용'의 답변 내용을 다시 표시해주세요.

프로그램 동작 에러

Hee Ku Kang — Fri, 31 Jul 2026 04:30:11 GMT

SDL Trados Studio 2019를 사용하고 있습니다. 프로그램이 작동하지 않는, 약간의 전 상담에 대한 답신에 따라 조치를 취하지만, 여전히 적용되는 것과 동일한 질문에 대한 답변이 시작됩니다. 프로그램 준비를 위해 다른 방법이 없는 시기를 알려드립니다.

프로그램 작동 에러

Hee Ku Kang — Fri, 31 Jul 2026 04:17:33 GMT

SDL Trados Studio 2019를 사용하는 사용잡니다. 프로그램이 작동되지 않아, 조금 전 드린 문의에 대한 답신에 따라 조치를 취했지만, 여전히 첨부한 바와 같은 동일한 에러 메시지가 뜨고 있습니다. 프로그램 정상 작동을 위한 다른 방법이 없는지 알려주시기 바랍니다.uat.community.rws.com/.../_D0C5ECB7_.tif

프로그램이 작동하지 않습니다.

Hee Ku Kang — Fri, 31 Jul 2026 01:05:55 GMT

SDL Trados Studio 2019 제품을 사용하고 있습니다. 프로그램을 작동시키려고 제품 아이콘을 클릭했는데, 프로그램이 작동하지 않고, 첨부된 파일과 같은 에러 메시지가 떴습니다. 어떻게 처리해야 하는지 알려주세요. 죄송하지만 빠른 답변 부탁드립니다.

update to Trados Studio 2024 SR1 - 18.1.4.6694

Caroline Amyot — Thu, 30 Jul 2026 18:26:13 GMT

Bonjour,

Did someone had issues with the up date to Trados Studio 2024 SR1 - 18.1.4.6694 with Studio?

We had a few users that were not able to use Studio after updating the software. They had to change computer.

Thank you!

Caroline

Match percentages disappearing

Mark Weatherall — Thu, 30 Jul 2026 03:36:09 GMT

After I returned a reviewed document to my client, they noticed that the match percentages for some segments had disappeared, as shown in the screenshots below. I used Trados 2026 for the review, while the client uses Trados Studio 2019. Is this a known issue, or could it be a compatibility problem between Trados Studio 2026 and Studio 2019?

There was an error in our system! Retrying in 55 seconds... Please contact support if the problem persists. Details | Logout

Ana Bardi — Wed, 29 Jul 2026 17:11:28 GMT

I am unable to sign in because I repeatedly receive the following message:

There was an error in our system! Retrying in 55 seconds...
Please contact support if the problem persists.
Details | Logout

The problem persists after waiting and trying again.

I was referred to this Community by Fran from the Licensing Team, who advised me to post my issue here so it could be investigated by the Support Team.

Additional information

I can reproduce the issue consistently.
The error occurs every time I try to log in.
I have already retried multiple times, but the issue persists.

Could you please advise:

What could be causing this error?
Is this a known issue?
Are there any troubleshooting steps I should follow?
What additional information (logs, screenshots, etc.) would help diagnose the problem?

Thank you for your assistance.