Mila Pruger

Can you confirm where you entered the LTR/RTL markers?  It might help if you created the screenshot with hidden chars showing.  

Can you also provide a sample text with just a few sentences in it we can validate?

Thank you for you reply, Paul!

The problem is in the source column, so LTR/RTL markers are not relevant. 

Here are two additional samples. 

In the first one you can see the problem with e-mail address:

In the second one you can see the problem with the number (271433 instead of 334172)

All these screenshots come from different documents from different clients. And in the original documents these segments look fine and there are no hidden characters. This never happened before, only since I installed the update yesterday.

Thank you for you reply, Paul!

The problem is in the source column, so LTR/RTL markers are not relevant. 

Here are two additional samples. 

In the first one you can see the problem with e-mail address:

In the second one you can see the problem with the number (271433 instead of 334172)

All these screenshots come from different documents from different clients. And in the original documents these segments look fine and there are no hidden characters. This never happened before, only since I installed the update yesterday.

Mila Pruger

Mila Pruger said:

The problem is in the source column, so LTR/RTL markers are not relevant. 

Can you also provide a source file that we can use to test that does this please?  Zip it and attach to the thread, or email it to pfilkin@sdl.com

Sure. Since I am bound with NDA agreements I cannot send you the complete files, but here are few samples of problematic texts that I copied from different files.

So I attach here a Word file with few segments that do not open well in Trados + a screenshot of the same file opened in Studio. You can see that the English text and also part of the Hebrew text is reversed (for example, RFGE instead of EGFR, ADF instead of FDA and ןונימב instead of במינון)

New folder (2).zip

Mila Pruger

Thanks for sending the file.  The source file doesn't actually contain any BiDi controls so I also get this:

However, if I insert a LTR marker in Word here:

Then when I open the file in Studio I see this:

Having said all of this I also appreciate that this was not required in earlier versions so we have clearly made some undesirable changes here and I can see that this is not an acceptable workaround if there is a lot of LTR text in the document.  I'll log this for further investigation with the support team.