Make the Translate extension be based on DOM, not strings
Open, Needs TriagePublic
Actions

Description

This is the fundamental issue at the heart of the Translate extension, which blocks it being nicely editable in VE, breaks section edit links or force you to make translators 'translate' wikitext syntax, and many other issues. It's mostly akin to "tear down the Translate extension and start again", though. :-(

Related Objects
Search...

Status	Assigned	Task
Open	None	T131516 Reduce or eliminate the need for the user to touch <translate> tags and unit markers
Open	None	T143327 Make the Translate extension be based on DOM, not strings
Open	None	T55974 Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension)
Resolved	Arlolra	T50891 Parsoid should support <translate> and <tvar> natively as they are not normal parser tags
Declined	ssastry	T105186 Support Translate extension in Parsoid
Resolved	Arlolra	T55874 Add a generic extension registration mechanism
Open	None	T49344 Internal nodes should eventually be in a separate document ("sub-documents")
Open	None	T171976 Invest in our future by researching a radically better multi-lingual content system (both reading and editing), compatible across all devices
Open	None	T270422 Visual diff behaves poorly on pages using Translate extension