Probability score: 0.8  

Question improvement suggestion: Provide the exact version of Trados Go you are using, as well as any specific error messages or codes that may appear during the import process.  

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

Hello,  

It seems you're encountering an issue with importing TMX files into Trados Go. Here are some steps and workarounds you can try to resolve the problem:

**Step 1: Validate the TMX File**  

Even though you mentioned that the TMX file is valid according to TMXvalidator, double-check for any specific attributes or tags that might not be compatible with Trados Go. Ensure that the header information is correct and does not contain any typos.

**Step 2: Check for Missing Target Segments**  

Open the TMX file in a text editor (like Notepad++) and search for translation units that have source segments but missing target segments. Remove any such translation units, as they can cause import failures.

**Step 3: Simplify the TMX File**  

If the TMX file contains overly long translation units, consider cleaning it up by removing any segments that exceed a reasonable character limit (e.g., 5000 characters). This can help avoid performance issues during the import.

**Step 4: Use Workarounds**  

- **Workaround 1:** Try importing the TMX file into Trados Studio first, then export it again and attempt to import the newly exported TMX file into Trados Go.

- **Workaround 2:** If you have access to Olifant, use it to open the TMX file and export it with the default style while unchecking options like "Export nodes" and "Export empty segments."

**Step 5: Check Language Codes**  

Ensure that the language codes in the TMX file are valid and match what Trados Go expects. For example, replace any incorrect codes like EN-AUS with EN-AU.

**Step 6: Increase Server Timeout**  

If you have control over the server settings, consider increasing the timeout settings in IIS for the TMService Farm to allow more time for the import process.

If these steps do not resolve the issue, please provide additional details about the specific error messages or codes you encounter during the import process, as this can help in diagnosing the problem further.  

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: Provide the exact version of Trados Go you are using, as well as any specific error messages or codes that may appear during the import process.  

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

Hello,  

It seems you're encountering an issue with importing TMX files into Trados Go. Here are some steps and workarounds you can try to resolve the problem:

**Step 1: Validate the TMX File**  

Even though you mentioned that the TMX file is valid according to TMXvalidator, double-check for any specific attributes or tags that might not be compatible with Trados Go. Ensure that the header information is correct and does not contain any typos.

**Step 2: Check for Missing Target Segments**  

Open the TMX file in a text editor (like Notepad++) and search for translation units that have source segments but missing target segments. Remove any such translation units, as they can cause import failures.

**Step 3: Simplify the TMX File**  

If the TMX file contains overly long translation units, consider cleaning it up by removing any segments that exceed a reasonable character limit (e.g., 5000 characters). This can help avoid performance issues during the import.

**Step 4: Use Workarounds**  

- **Workaround 1:** Try importing the TMX file into Trados Studio first, then export it again and attempt to import the newly exported TMX file into Trados Go.

- **Workaround 2:** If you have access to Olifant, use it to open the TMX file and export it with the default style while unchecking options like "Export nodes" and "Export empty segments."

**Step 5: Check Language Codes**  

Ensure that the language codes in the TMX file are valid and match what Trados Go expects. For example, replace any incorrect codes like EN-AUS with EN-AU.

**Step 6: Increase Server Timeout**  

If you have control over the server settings, consider increasing the timeout settings in IIS for the TMService Farm to allow more time for the import process.

If these steps do not resolve the issue, please provide additional details about the specific error messages or codes you encounter during the import process, as this can help in diagnosing the problem further.  

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