Content translation version 2 (CX2) is a major refactoring and architectural update ofContent translation (CX, or CX1 in this document).The goal is to provide a solid and reliable translation tool that is aligned with the Wikimedia standards in technology and design, and provides a great way to contribute for newcomers.

Version 2 uses theVisualEditor editing surface, anOOUI based front end, and follows theWikimedia design guidelines.

In addition, learnings fromexisting and new research on the experience of new editors will be used to identify improvements to make translation a great way to start contributing to Wikipedia.The plan is to gradually replace version 1 with version 2in several stages.A backwards compatibility plan will make sure that content created by users during the transition period won't be affected.

The new version is now the default, you can justaccess the tool from Special:ContentTranslation from Wikipedia in any language.When you start a new translation with Content translation you will be using the new version.Note that the previous version will be still used when opening old translations that you started with such version.

The new version is still in active development.Please, use it to translate articles and report feedback.We love to hear what works for you, and what still needs improvement.

Using version 2 on production will create content in real wikis when you publish your translation, so it is not suited for experiments that don't create a quality translation as a result.For more experimental testing, you can try the new feature inour testing servers.They are a separate wiki (you need to create a new user account since the log-in service is not integrated with Wikimedia projects).Although the content you translate in the test servers comes from real Wikipedias, the published content will be only created in the test server.This allows to experiment without interfering with the work done in those projects.

We areinterested in hearing how well the new version works for both new and existing users of Content Translation.

In addition, articles published with the new version are marked with the#contenttranslation-v2 edit tag to facilitate finding them (e.g., using Recent Changes) and evaluate the quality of the content.

The new version will include a more powerful editing surface, which will bring new possibilities that were repeatedly requested by translators using the tool.However, other features from version 1 won't be initially available with the new version.

A general CX2 roadmap describes the planned interventions in more detail.

The main areas of intervention are:

• Align with the Wikimedia standards in technology and design
  • Visual Editor's editing surface with more editing tools to insert and edit templates, tables, multimedia, categories, etc.
  • Reliable undo/redo support.
  • UI revamp based on UI Standardisation initiative and OOUI components
• Quality control mechanisms. Control user modifications in more detail toencourage translators to create quality content.
• A great way to contribute for newcomers
  • Machine translation support for Template params, reference texts and practically all kind of elements in screen. In version 1, machine translation was limited to paragraphs alone.
  • Better support for References and Templates
  • Ability to add and remove categories
• Solid and reliable
  • Fixing lots of bugs that was too difficult to handle with previous version

The features listed above are possible with the new technology architecture.However, in order to be able to deliver those improvements soon, we have to limit the efforts of rewriting all the existing tools CX1 has.Thus, some of the existing tools won't be available in CX2 initially.We selected those based on our observations of current use, the value they provide in version 1 and their complexity, but we arelooking for your feedback during this process.

These are the tools currently in CX1 thatwill be missing initially for CX2:

• Custom template translation editor. CX1 added support for a side-by-side editor of templates that allowed translators to map their parameters. The initial implementation allowed toevaluate a promising concept but it was far from being complete, and rewriting this for CX2 will require significant effort. Initially, the standard template editor dialog provided by Visual Editor will be available in CX2 instead. Although it is not optimized for transferring information across languages, it provides basic support for editing all parameters of a template in the translation.
• Dictionaries. CX1 had experimental support for dictionary information lookup for a few language pairs. Dictionaries are a very relevant tool for translators, and we'll keep track the progress of Wikimedia projects in this area that will enable their integration in the future. However, providing support for CX2 makes more sense when there is a clear plan to integrate more dictionaries.
• Progress indicator in the editor. A progress bar showed in CX1 how much of the article was translated and how much was missing. This information will be still visible from the dashboard, but not while editing the article. Based on our observations from users, having it on the editor was not providing much value.
• Announcements of new machine translation services. The automatic translation card became highlighted when a new machine translation service was made available for the current language. This was especially useful in the initial stages of the tool, where new services were added regularly. We can reconsider this feature once the migration to version 2 is completed, and we plan to integrate new machine translation services in the future.

Content Translation was developed iteratively for last 2+ years.During that time, the focus was to evaluate the core ideas on how to improve the translation experience for Wikipedia editors.The architecture was a flexible one where modules can be plugged and try these concepts.This allowed to move fast, but the approach and cut corners affected the code organisation, maintainability and reliability of the tool.The proposed refactoring and architectural update will contribute to provide a tool solid and reliable translation tool that is aligned with the Wikimedia standards in technology and design.

At the end of this intervention we want Content Translation to be a tool that:

• Is aligned with the Wikimedia standards in technology and design. Uses the editing surface technology ofVisual Editor (VE), and follows theDesign style guide principles.
• Is a great way to contribute for newcomers. The tool provides a quick and easy way for new editors to start contributing. Even if the tool does not support dealing with complex content or situations, it always provides a clear path forward for new editors.
• Is solid and reliable. The tool is reliable enough to go out of beta for at least one community.

The way to get there is detailed in different plans below.

Starting in February 2018,the CX2 roadmap defines the incremental stages to complete the development of the tool.

A rough plan is to enable version 2 in smaller wikis or subset of wikis to do QA and gradually rollout to more wikis. Thelist of representative wikis can be useful to identify candidates.

Versions 1 and 2 will coexist during a transition period. Given that the translations each version produce are not expected to be compatible, the following steps are considered to avoid issues related to breaking backwards compatibility:

1. Translations started with one version of the editorwill be always opened with the same version, regardless of which is the current default editor. That is, when version 2 is the default, old translations started with the version1 will still be opened with version 1.
2. Once version 2 is considered the stable default, creating new translations with older versions will be prevented. That is, version 1 will not be available to create new translations, but it will be still available to edit the old ones.
3. With a process in place toautomatically discard translations after one year, version 1 could be safely removed after such period pases since no new articles can be started with it.

For more recent activity related to Content translation (from July 2019 to nowadays), please checkthe Translation Boost Initiative.

Below are the archives prior to November 2019 (...andyes, both pages are overlapping between July 2019 and October 2019).

• Solvedregression that prevented published translations to be connected with the versions of the article in other languages through the language list.
• Better support for references wihthe integration of Machine Learning generated parameter mappings for common templates of the 15 most translated languages.
• Improved support to encourage content quality byadjusting the paragraph unmodified content limits to avoid false positives.
• More solid application of Machine Translation bypreventing error messages and scroll jumps.
• More solid identification of potential translators withimproved APi.

• Better support for referencesby highlighting references with a template that is missing mandatory parameters after being added to the translation.
• Improved support forISBN links by avoiding the creation of unnecessary markup, andmath formulas by preventing showing warnings when they are not modified in the translation.
• Better guidance byfixing the navigation through warnings and errors in the translation.
• Improvements in Translation stats toprevent technical errors.
• Better machine translation support byupdating Apertium with latest language packages.
• Better handling of templates byavoiding template style info to leak into the translation anderrors when references are inspected.
• More reliable autosaving and publishing withbetter support of complex contents such as math formulas.
• Better handling of templates byskipping template-specific styling that caused problems when transferred across languages.
• Supportchanges in AbuseFilter and SpamBlacklist systems.

• Better support for references bypreventing details to show when those are not really present in the reference.
• Improved discoverability by providingan updated invite to propose translating instead of creating an article from scratch,avoid unnecessary steps when searching for the article to translate, andsurfacing the persistent entry points in a more reliable way using global preferences.
• Better guidance bylinking machine translation quality-related warnings with the updated documentation, andpreventing escape key to proceed with publishing when getting the confirmaiton dialog because of warnings in the translation.
• Improved suggestions bysurfacing suggestions as the default view when users are not working on any translation already,making it possible to link to any specific view in the dashboard, providing smarter services tofind potential source articles for a given title in another language andpotential translators, anduse a more clear visual metaphor to keep suggestions for later.
• Improved support for templates bypreventing translation services to corrupt math markup, andpreventing "monospaced" template to break the rest of the translation.
• Improved support for comparing contents between source and target paragraphs by providingmore reliable highlighting of correspondign sentences anddivision of paragraphs.
• Better support for references byhighlighting and avoiding the publication of references with a template that could not be adapted.
  

• More solid creation of missing links byusing wikidata and machine translation to create a missing link label in the target language.
• More solid publishing process by preventingissues that could lead to translations being published in the wrong language.
• More solid loading process to avoid issues thatprevented to restore translations where users added a new reference. Preventing new translations to get stuck, and recovering those already stuck.
• Exploration to improve template support with Artificial Intelligence. Machine Learning approach used toobtain the mappings for frequently used templates on the most common translated languages.
• User researchreport published.
• More fluent process for inserting media byusing the article title as the initial search.
• More reliable generation of the published content by preventing internal IDs for translation segments to leakwhen publishing references andpasting content in Visual Editor.
• Better user guidance by flaggingissues with templates that can be created into the target language but their contents cannot be transferred because no parameter could be mapped or mandatory parameters are still missing. Providingspecific warnings to differentiate these incomplete templates from templates that could not be found for another language (missing templates).
• More reliable restoring process when the source article changed bymaking sure that the restored content uses the latest version only when it is safe to load without causing any parts of the user translation to get lost, falling back to the original version used to start the translation otherwise.
• Better support for exposing the tool as default bysupporting settings to disable the entry points for wikis where the tool is out of beta.
• Better guidance for users byshowing an invite to try the main entry point to those users that discovered the tool through a non-persistent invite so that they learn how to find the tool the next time.
• Better support for Simple English byavoiding to expose translation engines for translations involving English and Simple English, andpreventing Simple English to still show as missing after the translation is published.
• Better support for templates byidentifying more reliably when templates fail to transfer across languages, and avoidissues when transferring them.
• Better support for references byidentifying them more reliably on translation services that only support plain text such as Apertium.
• More reliable processing of the source document bysupporting different types of text blocks.
• Better user guidance byshowing warnings less eagerly, giving users more room for editing the content before the tool tells them there are problems to fix.
• Better support for templates bypreventing templates in the source document to be added as their rendered contents, loosing the template structure and propagating unnecessary HTML to the translation.

• Better guidance by providingmore clear messages to distinguish the issues related to unreviewed machine translation content for the document and for one paragraph. Alsousing standard icons, andavoiding confusing options in the menu.
• More reliable generation of the list of references byusing the correct template when it is available for a language.
• Better link support for Simple English by avoidingnew translations started from interlanguage links andlinks to Simple English in the translation editor to to lead to English Wikipedia instead.
• Moresolid restore process for saved translations to allow translators to work on multiple sessions more reliable.
• More reliable representation of the translation progress byrepresenting more accurately the percentage of machine translation.
• Improved device support byallowing access from mobile devices, mainly useful for tablets.
• Support for machine translationexpanded to support translations to Italian.
• More fluent process to start new translations bysimplifying the entry point on the interlanguage links.
• Improved support to encourage content quality byadjusting the unmodified content limits to consider the number of paragraphs affected and previous translations by the user.

• The new version isthe only version available for new translations, even when started through the URL. Old translations started with version 1 will still use it for backwards compatibility.
• Improved support for references bynot translating reference contents automatically since information such as book titles is often kept untranslated, andavoid warnings insisting to translate the contents of the reference list.
• Support forstandard visual components on the new translation dialog.
• Better guidance bycommunicating that publishing is only allowed to experienced editors for wikis configured in such way. Configuration has not been applied to any yet, and should make obsolete the use of abuse filters that some communities implemented.
• Better guidance by providingmore detailed publish options in a dialog andmore detailed information when users are not allowed to publish translations with too much unmodified contents.
• Improved persistency for templates bypreventing user changes to get lost across sessions.
• Better support forexploring links in the source document.
• Performance improvements byreducing the number of code modules delivered to users, and regressions correctedfor placeholder icons, andfor event logging of suggestions.
• Better user guidance bycommunicating the English Wikipedia limitation to only allow publishing toextended confirmed users in a more detailed way and before the user makes the translation effort.
• Better control to start a translation byallowing to select pages from different namespaces, not just the main (article) namespace. Some namespaces such as file, gadget, template or talk are still excluded.
• More reliable process forcorrectly restoring andpublishing translations that start with an empty paragraph.
• More reliable visual alignment of paragraphs between original and translated content byadapting to paragraphs becoming shorter andfixing regressions.
• More precisecalculation of the percentage of unmodified contents for the whole document, andcustom adjustments on a per wiki basis.
• Better connection between warnings and the affected content byusing color icons in the issue messages that match the warning or error marks in content.
• More reliable editing support byrecalculating the editing area size to elements that take time to load which prevent unnecessary scrollbars.
• Cleaner process for starting a new translation byreducing the terms of use text, andadjusting the edit area spacing for the translation title.

• Better guidance on how to get started byinviting users to add the first paragraph to the translation.
• Support for theautomatic removal of old translation drafts.
• Better tracking of user modifications to the content byignoring the list of references when computing unmodified machine translation.
• Improved machine translation support by correctingextra spaces introduced by Google translate, andavoiding references lists to be sent to translation services.
• Better guidance by showing an option to reset the translationonly when the user made modifications to the translation.
• Improved access to data on published translations byfixing wrongly formatted JSON exports.
• Better guidance bycommunicating session has expired.
• Improved development environment byreducing the building time due to unnecessary code dependencies, enabletesting for local wiki restrictions andinfrastructure (service runner) updates.
• More reliable rendering of the content bypreventing spell-checker and input methods to show for the read-only source article.

• Support toinspect elements in the source article such as references, templates and other content with non visible information.
• More reliable generation of the published content byavoiding useless divs and nowiki tags inside references to be generated.
• Better support for galleries byshowing the associated contextual tools, and correctingvisual alignment for the new translation dialog language selector.
• More scalable support for translation services bysimplifying the default configuration, and prevention oftranslation errors with external services.
• Better handling of translation contents bysaving links reliably, dividing the content in sections withoutthe "italic title" template to get in the way, avoidextra spaces to be added around headers and improved support foridentifying and highlighting corresponding sentences.
• Corrected regressions intransferring templates across languages which was not working after the integration of the new read-only mode andstyle glitches in the article title.
• Improved testing environment by correctingfatal errors when logging-in in the beta cluster.
• Cleaner representation of the source article byavoiding the input cursor to show for read-only content, and preventinglinks to wrongly show as red inside audio templates.
• More clear statistics, byclarifying the information shown andthe description of the output.
• Completed theclean-up of the backlog of old translation drafts, allowing to automate the process next.
• Better support for references byproviding appropriate forms depending on the type of template they use.
• More reliable navigation to the translation tile and the associated information byfocusing the input in the title when navigating to issues related to it, andpreventing the instructions card to disappear when completing the title edit.

• Publisheddeletion ratio comparison showing the percentage of deleted articles for those created with and without Content translation and how these evolved in time for the target wikis.
• Published thepercentage of translations compared to total article creations, showing how much translation has been used as a way to create articles since Content Translation was available in different communities.

• Improved error communication bysurfacing pending issues when publishing.
• More reliable navigation in the new translation dialog byopening links on a new window.
• More reliable control of unreviewed content byadjusting the thresholds of the warning, reducing false positives and more strictly checking content copied from the source article.
• Version 2enabled by default, users migrated are shown an explanatory message. It's still possible to switch to version 1.
• Better support for inline templates,keeping their contents in the translation as plain-text when the corresponding template is missing in the target wiki.
• Moreclear language for the translation options with a clarifying message when machine translation is not available for the selected languages.
• More fluent experience byavoiding scroll to jump after adding a link.
• Improved support for transferring templates across languages bymapping parameters based on their names when template metadata is lacking.
• More reliable generation of the published content byavoiding ID attributes to be included for tables, andkeeping HTML entities (includingspaces) when transferred into the translation.

• Improved saving process by avoidingsaving to be unnecessarily triggered when content is transcluded.
• More reliable notification for automatically deleted translationswhen the user is missing a local account in the current wiki to support backwards compatibility.
• Better guidance whenthe original article has changed too much and cannot be updated without affecting the current translation, and facilitating access to the updated contentin a separate tab/window.
• Invite is shown to encourage users to try the new version.
• Improved support for transferring templates bycommunicating when mandatory parameters (or no parameter at all) could not be mapped.
• More effective warnings for unreviewed content,not interfering with content that the user started from scratch.
• More solid integration of translation services by supportinga rate-limiter to prevent excessive request peaks and avoidingissues when the rate-limiter is unconfigured.
• Improved entry points by allowingurl-based campaigns to configure an edit tag to be used when the resulting translation is published.
• Improvednavigation across different errors and warnings on the translation.

• Measurements for performance improvements in the access to external translation services.
• More reliable template processing to avoidissues with templates to block paragraphs to be added to the translation.
• Better control of content quality byadding to a tracking category published translations with unreviewed contents ( you can check thetracking category list on any language for the category with the code "cx-unreviewed-translation-category").
• Improved support for links by correctinga styling regression.
• More reliable saving process bypreventing errors in the initial save attempt.
• Support forreferences added by name, references are correctly transferred to the translation even if their definition is in a different paragraph.
• Improved support for Apertium bymaking tests independent of the testing servers infrastructure, and updated dependencies (lex-tools,separable, andothers) that were needed forupdating the French-Catalan support.
• Support forblocked users, and partially-blocked users to access the entry points.
• Performance improved for theAPI access to translation services.
• Better monitoring of translation services forreal-time tracking of errors and availability (view dashboard), andweekly use of translation services over time (view dashboard).
• Improved support for links byupdating the link information after a link is added.
• Better guidance byallowing access to additional details from the issue summary.
• More reliable approach to measure content modifications byavoiding the content typed by the user to be counted as machine translated content when starting from scratch.

• Improved performance byprefetching requests to translation services in advance to deliver results immediately when users add a new paragraph,caching of API requests andan optimization of the caching system.
• More reliable saving process byretrying with an increased timeout after initial failure.
• More solid approach todivide the content into sections for the tool to handle, andpreventing errors when adding sections to the translation.
• Improved support for inserting media,preventing the media dialog to block the article.
• Better support for references solving issues whenediting references anddisplaying them.
• Improved control for excessive unmodified content byexcluding types of content where the warning is not relevant in order to prevent false positives.
• Better support for red links, generating as red linksonly for the missing articles the user confirmed, and avoid rendering them as regular links in the source document.
• Better guidance by delaying content warnings only while the user is editing butshowing previous warnings immediately when a translation is resumed.
• Improved alignment on RTL languages and a cleaner source article byavoiding noise characters showing from Visual Editor elements.
• More solid control of anonymous access bygracefully handling access errors.
• More reliable saving and recovering process topersist the contents when user switches between translation services, andavoid moving translations to in-progress when there are no further changes since they were published.
• Better guidance bycommunicating when templates could not be adapted.
• Better mapping references across languages by using Citoid metadata when mapping template parameters, avoidingissues with empty references andpartially adapted ones.
• More effective integration with translation services bysending a more compact version of the content HTML to prevent exceeding the translation limits, improving efficiency and security.A regression in this area was also fixed.
• Facilitate the access to the new version bycreating an outreach campaign link to be used in interactions with Wikipedia communities.
• Instrumentation improvements tobetter measure the issues translators experience.
• More reliable application of machine translation byavoiding quick manual modifications to be counted as machine translation, improvingsupport for quote templates by avoiding blank text blocks to be sent for translation,avoid the adaptation of transclusion fragments,improved logging for Apertium, andbetter handling of templates andlink attributes.
• More reliablevisual alignment of paragraphs between original and translated content.

• Basic control fortoo much unmodified content warning, showing a warning at the paragraph level when machine translation has not been edited enough.
• Basic control toprevent publishing translation with very little modifications in the whole document showing an error.
• More reliablehandling of failing Machine Translation services.
• Improved behaviour for"undo" when marking links as missing, andavoiding interference with saving.
• A#contenttranslation-v2 tag is added to published articles with version 2 to facilitate analytics. The usual #contenttranslation tag still applies to articles published with any version.
• Improvements in the issue communication system tosupport general issues that are not attached to a specific paragraph, andcode refactoring to reduce duplications with the progress tracking system.
• More reliable application of machine translation togracefully handle the failure of translation services, its application to references by avoidingrepeated cite tags andrepeated reference contents,a more reliable integration with Apertium.
• Communication ofsession expiration in the translation dashboard.
• Dashboard to showthe translations published with the new version andthe number of users publishing these.
• Support forswitching between version 1 and 2 to allow users to test the new version, andprovide access to information about the new version.
• Graphs formeasuring the number of translators and articles published with the new version.
• Optimization toreduce the amount of data required to adapt templates improving the time to save contents, andbetter visual display of templates.
• Improved support for templatesavoiding infoboxes to be missing on source articles, bettersupport for coordinate templates avoiding these to break the visual alignment of paragraphs, andsupport for adding the list of references without errors.
• More reliable saving processavoiding blanked sections to remain unsaved.
• Improved visual alignment of paragraphs toavoid new templates added to the document to break it.

• Warning for too much unmodified content per paragraph to prevent machine translation misuse.
• Improved template translation byavoiding the mapping of parameters that do not exist in the target language.
• Support forvideos, andinline images.
• Publisheda list of representative wikis that will facilitate focusing on the impact our work has towards the stated goals.
• Improved support forreferences that appear in several paragraphs, andcitation templates to avoid dirty markup.
• Performance improvements toavoid delay when typing in large article translation.
• More reliable application of initial translations by avoiding to leave the paragraph unusablewhen Machine Translation fails and whenswitching to not use machine translation.
• Improved issue communication system by allowing tomark issues as resolved for the current session,showing information about issues when they are relevant, andmore clear message when there is too much unmodified machine translation.
• More reliable processing of the content to avoidsome images not being displayed in the source article,bullet points to be skipped,wide images overflowing their column , andstub templates to avoid displaying them.
• Better support forcontent persistency when using the browser back button.
• Adjusted look for link information to improve consistency with Visual Editor and avoid code duplication.
• Support forkeyboard navigation across paragraphs in the translation.
• Support forcalculating translation progress at section level.

• Improved handling of sections with transcluded content, thatwere not recognised as separate paragraphs.
• Enabling access to tools whenediting rich content inside a dialog.
• Communicatethe default machine translation service andwaiting due to changes of service more clearly.
• Notifications for the deletion of old translation drafts,configurable period for deleting old drafts automatically andinitial runs of the script to support backwards compatibility.
• Adjustments in the dialog layout used to edit complex content to preserve the document metaphor, enabling the use of the tools column.
• Morereliable loading of articles avoiding instances of "page not found" error for existing articles.
• Better support to transfer content to the translation, includingreferences ,templates,links pointing to the same target, andavoiding errors when adding new paragraphs.
• Improved auto-save to better deal with sections that were added while the saving process was running.
• More precise timestamps for translations to prevent discrepancies due to local timezone differences.
• Linking automatically corresponding versions in other languages through Wikidata when the article is published.
• Refactoring of styles to better anticipate the effect of changes in the styling code and better align to Wikimedia standards.

• Script toclear very old translation drafts to facilitate future backwards compatibility, reduce conflicts due to outdated content and better use of database space.
• Showing a cleaner source article by the removal ofirrelevant templates,preventing links for existing pages to be shown as redlinks, andpreventing navigating away when clicking images.
• Optimization of the saving process to be appliedonly when changes occur, andmore reliable category manipulation.
• Improved machine translation use byshowing the loading indicator persistently,not showing machine translation options on dialogs,fluently switching to an empty paragraph when machine translation is not used, and avoidingunexpected scrolling andtechnical errors when applying machine translation.
• Communicate errors whentranslation title contains invalid characters and thetranslation title is empty.
• Communicate warnings whena page already exists with the same title as the translation.
• Improved link cardallowing to mark links as missing andavoiding duplicate cards when double clicking a link.
• Support formachine translation extended for Simple English.
• Discourage publishing empty translations byshowing the publish button initially disabled.

• Support for Captcha confirmation when target wikis request it.
• Layout adjustments tokeep article titles visually aligned, make visual alignment reliablewhen resizing the browser window, andavoid menus to hide behind the main content.
• Showing a clean source article by removingirrelevant sections andhidden categories.
• Definition ofsuccess metrics:number of newcomers,percentage of successful completion,number of errors, andtranslation survival.
• Support for links withnew link cards allowing to preview their content in both languages and manipulate links, support tosearch for links in the target wiki, andbetter control for text input cursor placement when editing links.
• Use ofupdated API for short descriptions which allows local wikis to override Wikidata default descriptions.
• Starting translations from a link is more fluent byautomatically selecting the article to translate.
• More reliable saving byincluding source information, and language selection toavoid duplicates.
• Improved testability:editor version is persistent when navigating from dashboard, andcaptcha support added in the test environment.
• Automatic translation card with options to select the Machine Translation provider from those available, copying the source text or starting from scratch. Modifications on the original automatic translations are kept persistent with an option to reset them.
• Improving thepersistence of categories and solving issues withmissing categories.
• Improvements incode modularization,API parameter consistency, and regressions in thevisual alignment of paragraphs.

• Improved approach tokeep source and target paragraphs visually aligned and highlighting consistentlyrepresented andapplied.
• Improved support forgalleries, images (toprevent accidental navigation),timelines,math formulas, andtables.
• Polishing on category support, includinglayout adjustments andsupport for long labels.
• Asking for confirmation when the translation is going tooverwrite an existing article.
• Loading process improvements to communicate the loading status.
• Backwards compatibility support byopening translations with the version of the editor used to create them.
• Tool support improvements toshow tool cards in the tools column (including Visual Editor Inspectors) andshow initial instructions only when relevant.

• Infrastructure changes to improvelinks metadata (to facilitate adapting links across languages), andimage support.
• Support forbasic publishing of translations (further work on communicating issues to be done).
• Support forcategory adaptation. Categories getadded to the translation automatically based on the existing ones, and userscan remove them oradd new ones.
• Layout adjustments to customizethe editing toolbar, thesticky headers andhow both fit together.
• Frequently requested features from VE are now available in CX2 with the new editing surface such ascopy&paste links,edit link labels,reliable undo/redo,insert new templates, andconverting wiki-syntax.
• Clean-up of the source article toremove irrelevant sections for the translation such as hat notes, metadata or links to sister projects.
• The version used remains persistentas part of each translation to support backwards compatibility, andas users navigate between the dashboard and the editor to facilitate testing.

• A basic side-by-side editor that would allow users to do a very manual translation. Many regressions after integrating the Visual Editor editing surface have been solved.
• Content persistency. The editor allows loading articles,automatic saving, andbasic restoring of translations.
• Work with source and translation next to each other:add content paragraph by paragraph to the translation andkeep paragraphs aligned.
• Layout reorganisation to align with the style guide.
• Improved testability.CX2 Test servers working again, and plans to support backwards compatibility.

• Content Translation