Pieter,

Have you looked at the Text_Wiki
<http://pear.php.net/package/Text_Wiki>PEAR package? I haven't used
it, only read some of the documentation.
However, it looks like it's well organized. It's broken down into parsers
and renderers and it's extensible in that new parsers and renderers can be
created. It appears to have built in parsers and renderers for BBCode,
Cowiki, Dokuwiki, Mediawiki, and Tikiwik. A port of this (or a similar
concept) might be nice to have in Zend Framework. I'm not sure what it would
be called, but maybe something along the lines of Zend_Parser,
Zend_Parser_Bbcode, Zend_Parser_MediaWiki, etc. The key point being that it
should be built to be extensible to new parsers and renderers, not the
specific name chosen.

On Jan 30, 2008 2:24 PM, Pieter Kokx <[EMAIL PROTECTED]> wrote:

>
> Hello,
>
> For a while, I was thinking of a Zend_Bbcode proposal, to tokenize and
> render BBcode on a very extensible way. But after a lot of thinking, I
> did get up on a more extensible way for parsing BBcode and other
> lightweight markup languages like Wiki code.
>
> Zend_TextParser should provide an extensible way to tokenize and render
> lightweight markup languages. So it would be possible to create your own
> language and/or make your own tags.
>
> I was thinking to split Zend_TextParser into two parts,
> Zend_TextParser_Tokenizer and Zend_TextParser_Renderer. The tokenizer
> part is just tokenizing BBcode or Wiki code into an array, which should
> contain all the information for the Renderer part, which is rendering it
> to HTML (or another markup language, it should also be possible to
> tokenize BBcode and render it into Wiki code and reverse).
>
> I did also create a proposal on the wiki for this:
> http://framework.zend.com/wiki/x/3KQ
>
> Regards,
>
> Pieter Kokx
> --
> View this message in context:
> http://www.nabble.com/-fw-general--Zend_TextParser-proposal%2C-ideas%2C-suggestions--tp15189906s16154p15189906.html
> Sent from the Zend Framework mailing list archive at Nabble.com.
>
>

-- 
Bradley Holt
[EMAIL PROTECTED]

Reply via email to