On Wed, 20 Feb 2002, Melvyn Sopacua wrote:
> PHP is handled via a mime-type mapping. > So - would something like this be even possible: > > <Files "*.pxml"> > SetHandler AxKit > AxAddTypeMap text/xsl Apache::AxKit::Language::LibXSLT > #???????? > AxAddTypeMap application/x-httpd-php mod_php > </Files> No the mime-types in the Ax directives are AxKit mime-types. You need to separately declare a language handler for that mime-type using AxAddStyleMap And of course somebody would have to write the language handler itself. > What would be the goal, in this conversion, would broadly ammount to: > 1) Apply an XML shell around legacy content > 2) Write a stylesheet which leaves the '<?php processing instructions' alone > and which marks them as CDATA. > 3) Pass the result to php Wouldn't PHP be a Producer, in Cocoon terminology? 1) hand the file to PHP, make it process it 2) take the result and turn it into an XML tree The (2) part is interesting. For legacy content you could perhaps use XML::LibXML's parse_html_string() function, but that does a bit of content mangling, so if your PHP page results are XML-compliant you could use parse_string(). Maybe you need two language handlers for PHP, for these two different modes. > The '<?php processing instructions' is probably a problem in itself, but I'll > leave that to when I'm trying to bring this into practice. > > Just want to know, what is possible. > > > > Best regards, > > Melvyn Sopacua > WebMaster IDG.nl > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > If it applies, where it applies - this email is a personal > contribution and does not reflect the views of my employer > IDG.nl. > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
