Michael Beijer 

Michael Beijer said:

I know that these files are fragile, but is it still really this bad?

I don't think it's bad - but it is fragile in that you need to maintain the structure.  I can recall being at a conference with the developer well over a decade ago where one of the memoQ founders discussed what we were doing and thought we were "very brave" to introduce the features we were making available for this because of the reality that users rarely do what we think they will!!

The segment ID is the place people often go wrong and lose this or break it when they work in other tools.  If you increase the size of the font you'll see it:

Maybe that's your problem?

Presumably you've tried comparing the before and after files to see where the differences lie?  Also compare the underlying xml.

Michael Beijer 

In fact this is a better view of the potential to break it.  In normal size they just look like simple dots... but they're not:

Hi Paul,

Yes, I was aware of those little numbers, although, oddly, there appear to be none in my current file:

Supervertaler recreates the file exactly, only changing the translations in the 4th column.

And as I said, it doesn't even work if I manually insert the translations into the (otherwise unchanged) bilingual review file right after it is exported from Trados. This is very mysterious.

I also got the following error on one of the occasions where it failed to import:

Michael Beijer

Indeed, I noticed that tracked changes was switched on in the exported file, so I tried manually pasting my translations into the empty Target Segment column, with tracked changes still on, but none of my translations were reimported into the project, even though I was not given an error (that time). Very frustrating.

Reimporting these files has never really worked properly for me. Sometimes they will import, sometimes they won't, and there never seems to be any discernible pattern.

Probability score: 0.6  

Question improvement suggestion: Provide specific details about the error messages encountered during the import process and the exact version of Trados Studio you are using.  

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

Hello!  

It sounds like you're facing a challenging issue with the "Update from Bilingual Review" functionality in Trados Studio. Here are some steps and considerations that might help you resolve the problem:

**Step 1:** **Check Track Changes**  

Ensure that the Track Changes feature is turned off in both the original and the bilingual review files. This can sometimes interfere with the import process.

**Step 2:** **Verify Tag Formatting**  

Make sure that the tags in your bilingual file are formatted correctly and match the original file. Any discrepancies can lead to import issues.

**Step 3:** **Test with a Simple File**  

Try creating a simple bilingual file with minimal content and see if it can be imported successfully. This can help determine if the issue is with the specific file you are working with.

**Step 4:** **Use Workarounds**  

If the direct import continues to fail, consider using the workarounds mentioned in the context:

- **Recreate the Review File:** Export a new review file, copy the target segments from the problematic file, and then attempt the import again.

- **Use the SDLXLIFF Converter:** If you have access to the SDLXLIFF Converter for Microsoft Office, try using it to import the bilingual file.

**Step 5:** **Check for Corruption**  

To check if your bilingual file is corrupt, follow these steps:

1. Open the SDLXLIFF file in the Editor view.

2. Go to File > Advanced Save > Save Source As and see if it saves successfully. If it does, the file is likely not corrupt.

**Step 6:** **Consult Documentation**  

Refer to the Trados Studio documentation or knowledge base for any specific error messages you encounter during the import process. This can provide insights into what might be going wrong.

If you continue to experience issues, please provide more details about any error messages you receive and the version of Trados Studio you are using. This information will help in diagnosing the problem more effectively.  

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

Michael Beijer  The bilingual DOCX format is not meant for translation, but for review ONLY. The target segments should not be empty. They should always contain translated text that a reviewer can change if needed. The change will be tracked via tracked changes.

If the target segments are empty and you enter a translation in the bilingual Word document, that translation will not be imported. This is per design since this is a format for review purposes only.

Aha, thanks, that's very helpful!

Supervertaler currently ignores the target side and takes the source side and translates it. It then exports a review file with both sides full. I will change it to work with Trados bilingual review files with both source and target full, and just copy source to target in Trados before exporting the file. Hopefully, this will work.  

I am also planning to add a proofreading mode to Supervertaler, which will then work with bilingual files (exported from Trados/CafeTran/memoQ), where both src and trgt sides have text, but that's for later. 

Hi Michael Beijer 

Michael Beijer said:

Yes, I was aware of those little numbers, although, oddly, there appear to be none in my current file:

Those numbers are formatted as hidden, so you need to set Microsoft Word to view the hidden text (pressing the button ¶).

I added some info on this in my help system: https://github.com/michaelbeijer/Supervertaler/blob/main/docs/guides/CAT_WORKFLOW.md

And in a warning pop-up in the program itself: