Hello! Wanted to report a few bugs after using the CXT for this translation. Hope it can be helpful.
- When inserting a comment (either through the ellipsis menu or starting to type
<!--), the viewport scrolls to the top of the screen - When a link is blue in the original language and red in the receiving language (the translation), it would be nice to have easy access to using the local language's title, e.g., with a single click, to avoid the mess of trying to edit within the VE to to the same.
- Additionally, would be nice to have {{ill}} accessible from a single click as well, when I want to preserve the link to an article in the original language while indicating that it's still red in the receiving language.
- I start to translate a heading and realize I don't want the heading at all but there is no way to delete that heading. I can only leave it blank.
- Had a major issue in which {{harvnp}} (in eswp) did not convert to {{sfn}} (in enwp) even though the two are associated in Wikidata. Reference support is a big deal. In the last article I translated with CXT, one of the refs was missing from the right-hand column (don't believe it was deleted from the draft, just never appeared) and was hard to restore—it was just poof, gone.
- re: harvnp, I was afraid to delete the redlinks to the template, hoping that they still retained their parameters. They did, so I regex'd the correct template name in later.
- Would be nice if common headings automatically translated (Véase también→See also, Referencias→References, Bibliografía, Enlaces externos, etc.)
- {{commonscat}} didn't translate properly from eswp to enwp either
- CXT displayed the template as wikitext and when I went to delete the text, the section retained the bullet point, which I cannot delete
- would be useful when publishing if the tool's edit summary also wrote out the originating wiki, for posterity
- ideally, could include the associated {{translated page}} template on the talk page, since users are unlikely to fill out the oldids on their own