> Sounds very cool :) At first glance I'm unsure whether it would require > creating a new Language module or if the XPS can be used as is?
I had to insert crude hacks into the XML::XPathScript modules (some functions get patched from inside the stylesheet :-), and so this behaviour would need porting to AxKit. Also I do not know exactly how well Axkit can perform the remaining phases of the PDF translation (TeX -> dvi -> pdf). > I don't think so :) Though maybe offline uses could go to the perl-xml list > (that might get us more new users -- you should announce your stuff there if > you haven't already as there are quite a few DocBook people there). I'm attempting this right now (if I manage to subscribe to the list :-). > Patches welcome ;-) Great! I just wish I could get some help on how to share the XPathScript engine between AxKit and the offline version. Anyone on the list interested? > IIRC Matt has started on that but bumped into issues (XML::XPath and > XML::LibXML have different worldviews, mostly because the former uses the > XPath OM and the latter the DOM). It may be that his old patches in that > direction were close enough that they can be worked on easily. OK I will dig through the list archives. Thanks! > > > * allow inline Perl/XPathScript code in XML documents through processing > > instructions: > > <?xml version='1.0' encoding="iso-8859-1"?> > > <?perl > > $randomStylesheetVariable=42; > > ?> > > Can XPS handle the processing-instruction() node test? If so, that could be > implemented in XPS :) Good idea too. -- Dominique QUATRAVAUX Ing�nieur d�veloppeur senior 01 44 42 00 08 IDEALX --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
