Integration of Content Translation (CX) and Visual Editor (VE) is supposed, at first, to change the contenteditable editing component to VE and preserve the current CX functionality—and nothing else. It is important to ensure that features already available in ContentTranslation are retained and these would specifically be:
**Loading the source article and the translation side by side.**
- **Initial load:** The source column must show a loading indicator. The translation column must have no content. The “+ Add translation” placeholder must be shown in the first section, or in other sections on hover.
- **Loading a saved translation:** The source and the target column must show loading indicators. The translated text must be loaded with the same content as it had when it was auto-saved.
**Clicking an empty section pre-fills the translation.**
- If the user selected “//no automatic translation//”, it must remain empty.
- If the user selected “//source text//”, the source text must be pre-filled with link, reference and template adaptation.
- If the user selected an MT engine, the machine-translated text must be pre-filled with link, reference and template adaptation.
**Manipulating content**
- Source and target paragraphs remain always aligned. If the user extends a paragraph in the translation by adding more content, the paragraphs below will be automatically pushed sown to keep the visual alignment.
- Hovering a source or target paragraph highlights in yellow the corresponding one. For the translation paragraph being edited, hovering a sentence will highlight in yellow the corresponding sentence in the source paragraph.
- A warning card is shown when there user have added automatic content without further editing.
**Copying and pasting**
- This is a bit of an open question. In CX currently we remove formatting on pasting; see T73308. This prevents various problems (although the bug report what they were), but also removes useful things like links and references (see T76571, T115182). VE handles pasting very cleverly when editing articles, so we may want to use it from the start. But if it requires a lot of additional work, we may want to go on with removing formatting in the MVP.
**Links**
- Link adaptation must work automatically when using automatic translation (see above).
- If text is selected in the target column that can be linked to an existing article in the target wiki, the link card must be shown that allows to link to it.
- It must be possible to add a link to a non-existing (“red”) target article.
- Clicking a link in the source column must show a link card with the source article (with title and image if available). If a directly corresponding target article exists, it must be shown, too. If not, the user must have the possibility to link to a different article.
- The appearance of the card to insert a new link may be brought closer to VE’s link inspector; or rather, VE link inspector can be reused with adaptations to CX—displayed as a card, allowing to link to a different target article
**References**
- No functional changes: Clicking a reference must show reference adaptation card.
- Not immediately required for MVP if it requires extra work, but will be required in the future:
- Edit the reference’s content
- Add a completely new reference that doesn’t appear in the source article
**Math**
- No changes: clicking must copy the formula.
- Not immediately required for MVP if it requires extra work, but will be required in the future:
- Edit the formula
- Add a new formula that doesn’t appear in the source article
**Templates**
- Use the new template editor
- Not immediately required for MVP if it requires extra work, but will be required in the future:
- Add a new template that doesn’t appear in the source article
**Categories:**
- No changes: Adapt the existing directly corresponding categories.
- Not immediately required for MVP if it requires extra work, but will be required in the future:
- Add a new category that doesn’t appear in the source article