Dorothea, Sorry for the late reply, catching up on email from the break....
I see you've already had your specific problem answered. But I'd like to chime in with a bit general advise. When doing development with XSL it's a pain to have it running live on the site.... as you pointed out. The errors are confusing and sometimes are pointing you in the wrong direction - or just don't give you any hint other than something went wrong. Typically when adding a new XSL feature I've found that it works best to download the a specific DRI page. Then in a separate IDE load the DRI page along with the XSL and debug it there in an isolated environment. We use Oxygen XML which is a low-cost, but not free, xml IDE ($48 USD for an academic license). It will allow you to step through the XSL one line at a time viewing the input, relevant XSL template, and the output all at the same time. Once we have the XSL working for one particular page then we load it back into Manakin to see if it works. If you find that it doesn't work in another case (i.e. on another page) take that DRI page and repeat the processes. I have to admit that this strategy work a whole lot better with Manakin 1.1 where METS documents were included inline. With DSpace 1.5 these documents are no longer included inside the single DRI page. Thus if the page you are dealing with requires references to METS documents you'll also need to download those documents as well and store them locally as static files. To make sure that the resolving works you'll then need to edit the original DRI page to adjust for the locally stored METS documents. Again, Hope this helps. Scott-- On Dec 18, 2007, at 3:18 PM, Dorothea Salo wrote: > If this is completely unworkable, feel free to scoff at me, but... > > Is there *any* way that Manakin can be nudged to give more information > about XSLT problems in a theme? As it is, when I break something > non-obviously (that is, not a gross XML well-formedness error), all I > can do is guess wildly what I just broke. Given that every Manakin > tweak means a Subversion commit, checkout, rebuild... this is > uncommonly tiresome and time-consuming when things break often. (And I > break stuff a lot.) > > Surely SAX knows where it is when a stylesheet blows up? Can it be > persuaded to disgorge that information? > > Dorothea > > -- > Dorothea Salo [EMAIL PROTECTED] > Digital Repository Librarian AIM: mindsatuw > University of Wisconsin > Rm 218, Memorial Library > (608) 262-5493 > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
