Topic on Talk:Content translation/Flow

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

Thanks for the feedback, @Czar. This is very useful. I'm adding more details below:

> When inserting a comment...

There was a similar issue with links that got fixed. However, I tried to reproduce the problem with comments and there was no jump. Maybe that was a temporary glitch. If the issue persists, please let us know indicating the browser you are using.

> When a link is blue in the original language...

We have plans to improve the way the target links are determined for missing links, as well as providing more options for selecting between the different options for the link labels. The linked tickets have more details on the proposed approaches, feel free to share any comments or ideas in this area.

> Additionally, would be nice to have {{ill}} accessible from a single click as well

That makes sense and is relevant for the context of translation, but has some additional complexity we need to evaluate. Although the template is relatively common (available in 59 languages), we prioritize for the tool generic features that do not depend on a specific template that a given community may or may not have. For now the ability to add any template should cover, and based on the data and observations we can consider facilitating the addition of specific types of templates for common cases.

> I start to translate a heading and realize...

The "Initial translation" card allows to make the content empty, which should be equivalent to just delete it. When publishing the content, empty elements should be skipped. If that is not happening, let us know and we'll investigate further.

> Had a major issue in which {{harvnp}}...

Good catch! I created a ticket to investigate this case. If the templates are connected in Wikidata it is strange that the equivalent one was not picked.

> Would be nice if common headings automatically translated...

Machine translation is available but not enabled for English. We are expanding machine translation support to more languages gradually. I captured your comment in this ticket requesting machine translation support for more languages.

> {{commonscat}} didn't translate properly

The issue seems to be that ihe contents for the template were already converted into wikitext for the source article (when displayed in Content translation). I expect that this won't be the case once we support for the source document an inspectable mode that presents content closer to Visual Editor edit mode. I created this ticket to check the status of the issue then.

> would be useful when publishing if the tool's edit summary also wrote out the originating wiki

The edit summary includes a link to the specific version of the article used for the translation, which includes the wiki in the URL. Are you thinking on any particular use where that won't be sufficient?

> ideally, could include the associated {{translated page}} template on the talk page

We considered supporting this as part of the publishing options. Given that these are community-specific practices where each community may use also a different template, additional efforts of supporting such configuration is needed. As I mentioned before, our priority right now is on general features, but in some future stage we can consider this kind of customization.

Thanks for all the feedback!