Probability score: 0.8  

Question improvement suggestion: Please provide the exact error message you receive, if any, when trying to access the Specific Language Pair option. This will help in diagnosing the issue more effectively.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello,  

It seems you're encountering a frustrating issue with the Specific Language Pair option in Trados Studio 2024 SR1, especially when working on GroupShare projects. Let's go through some steps to help you resolve this:

**Step 1:** Verify Compatibility  

Ensure that the version of the World Server Compatibility Pack you have installed matches your version of Trados Studio. You can check this by going to Help > About Trados Studio.

**Step 2:** Check Project Settings  

1. Open Trados Studio and navigate to Project Settings.

2. Go to Language Pairs > All Language Pairs.

3. Check if the Specific Language Pair option is visible. If not, it may be due to a compatibility issue with the GroupShare project.

**Step 3:** Workaround for Adding TMs  

If the Specific Language Pair option is not available, you can try adding your translation memories (TMs) under All Language Pairs:

1. Go to Project Settings > Language Pairs > All Language Pairs > Translation Memory and Automated Translation.

2. Add your TMs here and ensure that the option to use different translation providers is unchecked.

**Step 4:** Permissions Check  

Make sure that you have the necessary permissions to access the TMs associated with the GroupShare project. If you do not have access, contact your project manager to reassign the resources.

**Step 5:** Repair Installation  

If the issue persists, consider running a repair installation of Trados Studio:

1. Close all RWS applications.

2. Go to Control Panel > Programs > Programs and Features.

3. Select Trados Studio and click on Repair.

**Step 6:** Reset Settings  

If none of the above steps work, you might want to reset your Trados settings:

1. Close all RWS applications.

2. Navigate to the folder: C:\Users\%USERNAME%\App Data\Roaming\Trados\Trados Studio\.

3. Rename the XML files (e.g., Base Settings.xml, Plugincache.xml, User Settings.xml) to something like Base Settings_old.xml.

After performing these steps, restart Trados Studio and check if the Specific Language Pair option is now available.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

RWS Community AI

Probability score: 0.8  

Question improvement suggestion: Please provide the exact error message you receive, if any, when trying to access the Specific Language Pair option. This will help in diagnosing the issue more effectively.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello,  

It seems you're encountering a frustrating issue with the Specific Language Pair option in Trados Studio 2024 SR1, especially when working on GroupShare projects. Let's go through some steps to help you resolve this:

**Step 1:** Verify Compatibility  

Ensure that the version of the World Server Compatibility Pack you have installed matches your version of Trados Studio. You can check this by going to Help > About Trados Studio.

**Step 2:** Check Project Settings  

1. Open Trados Studio and navigate to Project Settings.

2. Go to Language Pairs > All Language Pairs.

3. Check if the Specific Language Pair option is visible. If not, it may be due to a compatibility issue with the GroupShare project.

**Step 3:** Workaround for Adding TMs  

If the Specific Language Pair option is not available, you can try adding your translation memories (TMs) under All Language Pairs:

1. Go to Project Settings > Language Pairs > All Language Pairs > Translation Memory and Automated Translation.

2. Add your TMs here and ensure that the option to use different translation providers is unchecked.

**Step 4:** Permissions Check  

Make sure that you have the necessary permissions to access the TMs associated with the GroupShare project. If you do not have access, contact your project manager to reassign the resources.

**Step 5:** Repair Installation  

If the issue persists, consider running a repair installation of Trados Studio:

1. Close all RWS applications.

2. Go to Control Panel > Programs > Programs and Features.

3. Select Trados Studio and click on Repair.

**Step 6:** Reset Settings  

If none of the above steps work, you might want to reset your Trados settings:

1. Close all RWS applications.

2. Navigate to the folder: C:\Users\%USERNAME%\App Data\Roaming\Trados\Trados Studio\.

3. Rename the XML files (e.g., Base Settings.xml, Plugincache.xml, User Settings.xml) to something like Base Settings_old.xml.

After performing these steps, restart Trados Studio and check if the Specific Language Pair option is now available.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

RWS Community AI

DİLARA YAMAÇ 

This is then a change in the GroupShare behaviour and has nothing to do with your own Trados Studio. 
You can simply add your TM in All Language Pairs. Should this be not possible, then the settings have been locked by your project manager. You still can try to create your own local project with the SDLXLIFF from the GS project and add both GS resources and your own resources there. When finished, simply copy the SDLXLIFF back in its previous folder, overwriting the original SDLXLIFF. Then deliver GS project as usual.

Thank you for your suggestions.

I would like to clarify that this issue occurs only after the last two updates of Trados Studio 2024. I can open and work with the same GroupShare project without any problems in Trados Studio 2017, or even in the previous versions of 2024. I can add my TMs in All Language Pairs but they do not function properly when using concordance, and sometimes I receive the message "no open translation memories".

I understand the workaround you suggested, and I can use it if absolutely necessary, but it is disruptive to my normal workflow, making the process inefficient.

Thank you again for your time and assistance!

Dilara