Topic on Talk:Content translation/V2

First of all, thanks for your work, it is faster and more powerful. My thoughts:

1. When inserting a template, I want it to allow the selected text to be filled (transferred) to a field (template parameter).
2. When choosing a link - Edit, it should provide two fields to allows modify the existing text and target instead of just entering a new target to replace it.
3. I want a button within right panel to remove the native text from an existing blue link, i.e. remove piped text from a link, for the local article name is appropriate.
4. One icing on the cake, if you allow one-click to mark all gray (does not exist for local wiki) links to missing (red links). It can be for the section or the article, and better if it supports placeholders (used to fill in Translink).
5. Bug: I see the "Mark as missing" has no effect, and no network requests or errors are triggered. It happened when I translate the Receiver_autonomous_integrity_monitoring to Chinese, and I see the link was marked as missing in the final submitted article.
6. If the toolbar buttons and menus are customizable / sort by frequency, it will be more flexible but obviously complex.
7. A little awkward, the inserted template be capitalizing the first letter of template name.

Thanks for the feedback, @YFdyh000. I'll provide some comments below:

1-3. Template insertion and link editing mostly reuse the standard behaviour provided by Visual Editor (VE). Regarding (1), it makes sense for inline templates (especially those with one parameter to have a way to quickly reuse the selected text. @Deskana (WMF) may be interested in the suggestion for VE. Regarding (2), Visual Editor team is exploring some options (more details in this ticket) which may help also with (3).

4. Makes sense, I created a ticket to capture the idea.

5. Since the new version uses a new editing surface, some tools still need to be rewritten to work with the new surface. The "Mark as missing" action is still in the works but expected to be completed soon (more details in this ticket).

6. For the case of Content Translation it would be good to investigate which are the specific editing tools that are used more often since the translation case (where the format is often inherited from the source content) may be different than regular editing, and we may consider reordering the options based on that.

7. This is expected to work like in VE. I'll check if there is anything causing an interference on the Content Translation side.

Thank you for your detailed answer.