Topic on Talk:Content translation/V2

In production, but many problems

4
NicoV (talkcontribs)

I see you have put V2 in production in frwiki for about a week. I checked the last 5 translations done with the new version, and not one is free of problems... I've reported the problems in Phabricator : T213255, T213256, T213257, T213258, T213259.

I checked a few more edits: T213262, T213273, T213275, T213276, T213277.

Has it been really tested before being put in production?

Pginer-WMF (talkcontribs)

Thanks for the reports, @NicoV.

Version 2 is an opt-in feature that is available for Content translation users. We are making version 2 more visible for existing Content Translation users as it gets improved in order for them to transition from version 1 to version 2.

Version 2 uses the Visual Editor editing surface which provides a more solid experience editing wikitext compared to version 1. Version 2 is still in active development, and we have processes to test, get feedback and improve.

Given the diversity of the content, the number of languages supported and the many templates that exists on each wiki (that were not designed to be transferred across languages), it is not feasible to anticipate all the problematic combinations, and we appreciate the reports to identify such issues.

I know that similar issues about the quality of the wikitext produced were reported in the past for version 1. Those were hard to fix in version 1 without making a big architectural change. Version 2 represents such change, many of those have been already fixed, and it is in a better position to get more fixed.

NicoV (talkcontribs)

@Pginer-WMF I do understand this should be an opt-in feature, but as it is still beta (and still generating a lot of problems in the results), why do you advertise it so much? For example, I've disabled CX in my preferences (beta tab), but I still get popups messages to use it whenever I end up on a page that was deleted because it's not admissible... Why don't you only give notifications to users that have explicitly requested to receive them, rather than forcing them on users who requested not to have them?

Also, why don't you give more prominent message to explain that CX and CX2 is "beta" software and that users opting in should check the result of their translation, especially if they create translations in the main namespace?

CX has been creating buggy articles in production for 3 or 4 years now, and it keeps doing so: when will something really be done about this?

NicoV (talkcontribs)

And when you say "it is not feasible to anticipate all the problematic combinations": I would agree if the problems were on a small number of edits, but they appear on a vast majority of articles. For example, I just checked 1 translation, and I reported T213419...

Reply to "In production, but many problems"