Various RFCs that seek to evolve wikitext which can help with the goal of addressing technical debt in content.Evolving wikitext - all these projects are on hold now.Specifically, we are assisting the Editing Team in its talk page reboot project.Addressing needs of editing products deployed on the Wikimedia cluster ( VisualEditor, Flow, Content Translation, bots) and non-editing projects ( OCG, Google, Kiwix).Addressing other functionality gaps and bugs.Picked up work related to task T118517: Using the tag for media markup.Picked up work related to T43716: Language variant support in Parsoid based on Finite State Transducer formalism ( T191925).We are working on an Extension API for extensions to hook with Parsoid.We are extracting an abstract Parser class that the legacy parser and Parsoid can both extend.It is still at least an year (if not longer) away. As of May 2019, we are working to prepare Parsoid to be used for all wikitext use cases within MediaWiki, initially only on Wikimedia wikis.As of Dec 20 2019, we have switched over all traffic from Parsoid/JS to Parsoid/PHP.As of Jan 2018, we started work in earnest to move Parsoid into MediaWiki Core by porting it to PHP.Parser Unification as part of the Platform Evolution Cross-Departmental Program.As of April 2017, Tim and Kunal are now part of the Mediawiki Platform team. Since May 2015, the erstwhile Parsoid team was rebranded as the Parsing team and the core PHP parser and Parsoid were brought under the purview of the Parsing team - this coincided with Tim Starling joining the group. Prior to May 2015, the erstwhile mediawiki core team was responsible for the mediawiki core PHP parser and the Parsoid team was responsible for Parsoid. (Parsers) Unified reusable parser library for reading as well as editing.(Tools) Support tools such as Visual Editor, Content Translation, Wikitext Linting, and others.(Out) Making our rendered content more standards-compliant and easier to analyze.(Modify) Support robust and reliable content modification, via wikitext, HTML, or beyond.
Email parser php code#
4 Code repositories that the Parsing team is either directly responsible for or shares responsibility with other teams.
0 kommentar(er)
