Re[2]: [PEAR-DEV] Pre-Proposal: Text_Wiki

Hi, >> I think you should divide this in several parts: [...] > > That is exactly the plan Great! > I will say that I do not intend to address XMLish source markups at > the start -- I think that is more the domain of XML parsers, not > structured text parsers. If you propose a standard way for developing translation components, there could (should IMHO) be XMLish ones. > However, I do intend to include at least one XML render class (well, > XHTML) so that Wiki-source can become XHTML. [...] > To reiterate: the plan is to have one Text_Wiki "master" class > handle the transformation interface in general, with a set of > interchangeable "source/parse" and "output/render" container classes > with rulesets for the specific transformations. > The "parse" classes parse text conforming to a source ruleset (e.g., > Tavi-style wiki, PHPWiki, SPIP, StructuredText, etc) into a Text_Wiki > meta-standard (an array of meta-keys indicating "bold starts/ends > here", "this is a header", "don't process this", etc., with the > associated text). The plan is great, but I don't think the name is. I'm not sure the Wiki format is the best one to take as the "master" or "pivotal" format. It would be better to take an XML format so that most of the translation components will benefit from XML/XSL capabilities. > Finally: can I get some preliminary votes on the package name > "Text_Wiki"? Or is this not the proper time? +1 for the package, but -1 for the name. -Nicolas -- Nicolas "Brush" HOIZEY Free PHP projects http://www.phpheaven.net Veille tous azimuts http://www.gasteroprod.com Clever Age http://www.clever-age.com