Reply to thread

Message: [QUOTE="keshlam, post: 3477785"] The only thing that needs 2.0 is the redirection -- which is irrelevant. Commented it out for debugging under 1.0. Fixing the various line wraps was a pain. Generally it's easier for everyone if you put the files on a website somewhere so they can be downloaded intact, rather than risking the newsgroup tools mucking with them. You say the failure's in the template for item-wrapper in string mode. The appropriate test is to see what the output of that template is. Quickest approach is changing the root to just apply-templates against //item-wrapper in that mode. Sure enough, that template produces no output; your change forces some non-empty output into it. David is absolutely right. So the thing to investigate is why you expected this template to produce non-empty results, not why forcing non-empty results has an effect. You asked the wrong question. Go back and ask the right one. Divide-and-conquer works wonders. xsl:message can also be a lifesaver, for displaying where you've gotten to and what some of the values are. Standard pointer to my DeveloperWorks articles on "styling stylesheets" for a way to automatically insert some stylesheet tracing information. [/QUOTE]