Thanks Yossi Rozenman 

There were many changes in this release in the Editor, and we did work with some BiDi translators in the Beta to make sure we had this covered as the initial Beta had some problems which were ironed out.  

I added a short video as I tried to repro this and can see one problem, although I don't know how you lost that many tags:

Perhaps you can provide your steps exactly so we can reproduce in full?

I also put my sdlxliff here to make testing easy:

Keywords.docx_en-US_he-IL.zip

 Bogdan Costisor 

Hi Paul, thanks for the prompt answer.

This is how the segment looks before I insert the RTL Unicode control character:

Now I will insert the RTL control character between "Scala" and ;

First, without tags so you can see how it should look:

You can see the RTL symbol and that the words order changed.

Now with the tags:

The tags and some of the text disappear. They are there, you only don't see them. Of course, it is impossible to work like this.

In the TM results pane you can see how it should look:

Thanks Yossi Rozenman I'm sure that will be helpful for the team working on this.

Yossi Rozenman  Thank you for the step by step. I managed to reproduce this. As Paul mentioned we moved the editor to the newest technologies and at this stage it's almost a brand new editor. This, combined with little beta support on the RTL, means that it will take a little more time to get everything fixed.

Support can log a CRQ on this. 

The file was very useful, thank you Paul 

I really hope you will fix it ASAP Bogdan Costisor , since it is very uncomfortable to work like this.

And if you are already fixing RTL issues, there is another issue with RTL and LTR Unicode control characters.

Many times I have to add LTR Unicode control character before or after numbers. This makes Studio flag it as number localization error. If you could make Studio ignore Unicode control characters before/after numbers and not mark it as an error, that would be very helpful.

Yossi Rozenman Thank you for your help in this thread. We'll coordinate with our technical support team to initiate the Change Request (CRQ). Once the technical support team have reproduced the problem and raised the CRQ our development team will plan the necessary work. At this time, we can't provide a specific timeline for when this process will be scheduled. We appreciate the information you've shared in this thread. If further details are required, rest assured that we'll reach out to you. Contact will be made through the email address associated with your Community profile. Support Case Id : 00808252 .