in reply to Difficult XML presentation issue

In the past, I have found that XSLT can be an extremely powerful searching and filtering tool, as well as a good presentation/transformation tool. I cannot say for sure that it would work in your situtation (because I am not sure i understand your problem 100%), but it might be worth looking into. You may be able to kill two birds with one stone here too, using the XSLT to do the searching and HTML conversion. The trick with XSLT is to think declaratively, but given what I have seen you do with reg-ex's in the past, I doubt you will have any trouble with it. There is always X-Path & XQL (not sure what they are calling them now), which can do some really interesting stuff as well.

I always like to try and use other XML based technologies with XML, they tend to be a good fit, and they up the project buzzword quotient signifagantly too.

-stvn

Replies are listed 'Best First'.
Re: Re: Difficult XML presentation issue
by inman (Curate) on Feb 03, 2004 at 13:56 UTC
    I have noticed that the transformation engines such as xalan can be memory hungry when large conversions are taking place. The solution to this is to divide the XML content up before transforming.

    The transformation that caught me out was on an XML file that was 200Mb in size. Assuming that the book isn't too large (e.g. 2Mb of XML) then you will have no problem using XSLT. W3 Schools have a nice xslt tutorial.

      inman

      Most DOM based parsers and transformation engines can be HUGE memory hogs since they need to load the whole document in memory. I have found though that SAX based parsers and transformation engines are much less hoggish and many times faster. Being stream based too they are ideal for online/real-time web transformations.

      -stvn