On 05/19/2014 10:55 AM, Bartosz Dziewoński wrote: > I am kind of lost in this discussion, but let me just ask one question. > > Won't all of the proposed solutions, other than the one of just not > expanding transclusions that can't be expanded to wikitext, break the > original and primary purpose of ExpandTemplates: providing valid parsable > wikitext, for understanding by humans and for pasting back into articles in > order to bypass transclusion limits?
Yup. But that's the case with <domparse>, while it's not the case with <html> unless $wgRawHtml is true (which is impossible for publicly-editable wikis). > I feel that Parsoid should be using a separate API for whatever it's doing > with the wikitext. I'm sure that would give you more flexibility with > internal design as well. We are moving towards that, but will still need to support unbalanced transclusions for a while. Since special transclusions can be nested inside of those we will need some form of inline support even if we expand most transclusions all the way to DOM with a different end point. Also, as Daniel pointed out, most other users are using action=expandtemplates for entire pages and expect that to work as well. Gabriel _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
