Hi Jim, Courtney!
Thanks very much for the suggestions. I'll try out the ideas you've mentioned. I'll update you of my findings.
It just seems to me that if MWiki allows custom tags, then it should allow a reasonable number of embeddings of custom tags within custom tags.
That is, it should take the innermost custom tag, evaluate it, then use it as $input to the enclosing custom tag, evaluate it, and so on... until we've reached the outermost custom tag, and then convert to the final XHTML.
Do we see some shades of recursion here?
Filip
Send instant messages to your online friends http://uk.messenger.yahoo.com
It just seems to me that if MWiki allows custom tags, then it should allow a reasonable number of embeddings of custom tags within custom tags.
The MWiki code doesn't know what to expect inside the custom tags (wikitext, html, plain text, some kind of delimited data, etc), only the extension code knows that. Therefore, shouldn't the extension be the one to handle parsing the contents of custom tags? Just pass $input through $parser before doing anything with it if you are expecting wikitext as input.
On 28/07/07, Thomas Dalton thomas.dalton@gmail.com wrote:
The MWiki code doesn't know what to expect inside the custom tags (wikitext, html, plain text, some kind of delimited data, etc), only the extension code knows that. Therefore, shouldn't the extension be the one to handle parsing the contents of custom tags? Just pass $input through $parser before doing anything with it if you are expecting wikitext as input.
...examples of which can be found in various extensions in Subversion, including Cite, Poem, etc.
Rob Church
mediawiki-l@lists.wikimedia.org