Is this not just T105447: [Epic] replace plain contenteditable with VisualEditor in ContentTranslation?

I wouldn't be at all surprised if it was. Do you want to merge them?

It's not entirely clear to me whether the user wants VE to have CX as an operating mode, or just to use (mostly) the same interface when using CX. They're a bit different.

I have a bit of a déjà vu: T120476 :)

In T121475#2004759, @Jdforrester-WMF wrote:

It's not entirely clear to me whether the user wants VE to have CX as an operating mode, or just to use (mostly) the same interface when using CX. They're a bit different.

I've asked the original reporter to clarify in https://he.wikipedia.org/wiki/שיחת_משתמש:בנימין#ContentTranslation_and_VisualEditor .

My suggestion is slightly different than Amire's. In my opinion, the translating tool should just be a mode of the visual editor (that is what I meant by merging). I don't think there is a point sepearting those two features: translating is just one method, of many, to write or rewrite an article. In CX, there is quite a strict editing limitation: You can not add your own paragraphs, for example. The limitations are not neccesary, but various features such as side-by-side view, quick image and paragraph addition will be very useful when creating or editing an article.
Another aspect: In CX's current form, there are two types of articles: those who are saved as a translating tool draft, and normal articles. I think translated articles should be treated just like normal articles: when editing them, there should be a translating option. It does not have to be exactly in its current form.