Page MenuHomePhabricator

Merge the Content Translation tool and VisualEditor
Closed, ResolvedPublic


The concept of the content translation is very good. The largest editions of wikipedia (especially the english) are main source for articles in other languages. But in the current form of the Content Translation, you can only translate an article, but cannot add information from other sources, add local tamplates, or even change/add media files, until you publish the article. My suggestion is to merge the content translation and the visual editor into one tool, in which translating would be an option. בנימין (talk) 15:16, 10 November 2015 (UTC)

This card tracks a proposal from the 2015 Community Wishlist Survey:

This proposal received 5 support votes, and was ranked #86 out of 107 proposals.

Event Timeline

DannyH raised the priority of this task from to Needs Triage.
DannyH updated the task description. (Show Details)
DannyH subscribed.
IMPORTANT: If you are a community developer interested in working on this task: The Wikimedia Hackathon 2016 (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please REGISTER NOW.
ori renamed this task from Merge the content translation and the Visual Editor to one tool to Merge the Content Translation tool and VisualEditor.Feb 6 2016, 12:31 AM

I wouldn't be at all surprised if it was. Do you want to merge them?

It's not entirely clear to me whether the user wants VE to have CX as an operating mode, or just to use (mostly) the same interface when using CX. They're a bit different.

Jdforrester-WMF moved this task from To Triage to Freezer on the VisualEditor board.

It's not entirely clear to me whether the user wants VE to have CX as an operating mode, or just to use (mostly) the same interface when using CX. They're a bit different.

I've asked the original reporter to clarify inשיחת_משתמש:בנימין#ContentTranslation_and_VisualEditor .

My suggestion is slightly different than Amire's. In my opinion, the translating tool should just be a mode of the visual editor (that is what I meant by merging). I don't think there is a point sepearting those two features: translating is just one method, of many, to write or rewrite an article. In CX, there is quite a strict editing limitation: You can not add your own paragraphs, for example. The limitations are not neccesary, but various features such as side-by-side view, quick image and paragraph addition will be very useful when creating or editing an article.
Another aspect: In CX's current form, there are two types of articles: those who are saved as a translating tool draft, and normal articles. I think translated articles should be treated just like normal articles: when editing them, there should be a translating option. It does not have to be exactly in its current form.

Pginer-WMF claimed this task.
Pginer-WMF subscribed.

The new version of Content translation integrates VisualEditor editing surface, allowing to use most of the tools and exposing services such as machine translation to be used also in Visual Editor and other tools if needed.