Re: [Text_Wiki] update on mediawiki parsing

Bonjour
Quinn Comendant wrote:

>Y'all
>
>What is the status of the mediawiki renderer? What is the current TODO
>list? I've been interested in helping with this dev (for almost a year
>now) but have only now gotten some free time. Let me know what needs to
>be done.
>
>Quinn
>
Sorry, Text_Wiki_Mediawiki package currently offers only the parser 
side, so you can only parse Mediawiki markup but not yet render it.
Anyway, it's quite easy to build if someone needs to convert toward 
Mediawiki syntax.
(reading the title, I assume you were meaning "parser", in fact)

For the Mediawiki parser side, the last release was very incomplete. I 
currently work on completing it. A very next release is in target.
However, as it is conditionned by some global refactoring of Text_Wiki 
itself, this Text_Wiki_Mediawiki 0.1.0 release will take place only 
after the next Text_Wiki one, 1.1.0 as we add features but keep BC and 
stability.
This Text_Wiki release will correct some bugs but also introduce a 
Singleton() factory, put in common methods to render complient text and 
urls  and some dynamic load of render objects, what I hope will save a 
few bytes in memory usage and some litle processing time.

Now, what is needed from you g(irl|uy)s is some more tests  of the CVS 
versions of Text_Wiki or any of its subpackages so we ensure BC.
This validation is peculiarly needed  for Text_Wiki_Mediawiki parser as:
- we introduce/complete parsing rules,
- this parser is quite experimental, as we "pack" together some rules, 
Strong+Emphasis+(very=sum of both) and Image+Wikilink+Interwiki (I'm 
just on this one).

Btw, the Image rule with some "link" attribute is very strange (Moritz 
?) and I cannot find it in Mediawiki references. I plan to set it back 
to the right syntax, please tell me if we need to keep this strange 
link=... one.

As a note, the (also new) Docbook render is still very incomplete but is 
the next in my list.

Now, anybody is welcome to complete/correct any of Text_Wiki and subs 
packages as you, Quinn, ask.
The way to follow, apart answering here, is to use the bug tracker, and 
register some Bug / "Request For Extend" with a link to corresponding 
unit patches (diff -u against CVS version) on some server you access.
Then, if you think you can spend some time for the community, we will be 
very happy to welcome you by pear devs.

I stay at your disposal for any question.
-- 
toggg

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php