https://bugzilla.wikimedia.org/show_bug.cgi?id=41716
--- Comment #37 from Gabriel Wicke <[email protected]> --- David, Roan, Scott, Subbu and me met in the office to discuss this. Short summary of the plans for the next steps: 1) Find nesting issues and see if we can fix them up with a bot. Also investigate use cases for markup in variant conversion rules. 2) Parse all -{ }- syntax and represent it in the DOM. Exact spec TBD in https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Language_conversion_blocks. Render the default variant according to the fallback chain for output-producing rules. 3) Enable editing of inline (once-only) rules in the VE. Most rule table modifications seem to be templated and will not be applied, so are not directly relevant. Rules that only modify the table but produce no output directly in page content can be represented as mw:Placeholder and will simply be preserved. This will make the VE usable for typical editors on variant-enabled wikis without requiring the variant conversion overhaul to be done first. For the longer-term strategy, we (mostly) agreed on: 1) Add the capability to associate an ordered list of glossaries with a page. These can either be stored in a separate namespace, or something like Special:Glossary. They should be revision-controlled and machine-readable for processing and UI purposes (JSON). 2) Add the capability to add page-specific rules that override glossary rules. Only glossaries and global rules associated with the top-level page itself are considered. This makes the set of conversion rules independent of dynamic template expansions. 3) Apply the combined rule set to the entire page including templated content. Rationales: * Simple mental model * efficient to implement * consistent conversion of passed-in content, even if it is massaged further during transclusion expansion * content in templates (labels, also real content in some infoboxes) themselves can still be protected or converted differently with local inline rules, as is done right now The details on how this can be implemented depend on whether we reach our goal of implementing multi-part revision storage that we can use for metadata by the next quarter. PS @David: Conversion rules should be passed into a pure function that converts each template expansion. Nothing at all should leak- otherwise our function would no longer be pure, and we could no longer efficiently update template expansions independently. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
