Actually, my thoughts on the parser are something
like this:
- The translation from wiki-text markup to tag markup is pretty
easy, almost just a search and replace. To correlate errors with lines
in the original document, attributes or tags can be added for line
number information.
- The resulting document can be made into valid XML just by adding
the necessary headers and the enclosing root node.
- The result can be validated with PHP's XML parser.
- Since the XML parser is written in native code (presumably as
opposed to PHP) it's probably faster than what we have now.
Translating from XML to markup should be equally easy by using the XML
document and the XSLT processor.
I know that the TPL serves as a framework for making calls into PHP
objects and plugins for the purpose of getting substitution text. If
we ever did allow some programming language other than PHP, the TPL
processor is what would need to be extended. For now, it's not an
issue as all we're talking about is how to markup text that will all
become HTML. Right?
Paul
Daniel T. Gorski wrote:
On 29 Mar 16:12, PAUL HANCHETT wrote:
Here is a somewhat disjointed proposal for enhancing coWiki's
abilities. How can we make this better?
Anyway you rape the parser: be aware that every <plugin> behaves like a
standalone PHP script that can do anything a script can do ...
... and get finally a valid XML result!
And of course KISS.
regards dtg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxx
|
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|