Recent content by spiel2001

MrTom -- Doh! That did the trick. Thanks again.

Oops -- found the problem with the HEIGHT and WIDTH values in the STYLE section of my SPAN elements. Seems Dreamweaver has a bug in it... it enters WIDTH and HEIGHT as WIDTH=Xpx and HEIGHT=Ypx instead of the WIDTH: Xpx and HEIGHT: Ypx form that it should be in. Just a heads up in case anyone...

I realize this is a tad off-topic for this board... but since you seem familiar with this library... two questions for you: 1) any idea why LIBXSLT is stripping the WIDTH and HEIGHT values off the STYLE attribute in my <SPAN> statements? It's messing up my page formatting as none of the spans...

MrTom -- Thanks. I was debating whether or not to give those a go but couldn't find anything that addressed their speed or reliability. Thanks for the confidence boost. Think I'll give them a go and will report back on the pain level when I'm done ;)

On this subject -- Two products I've found that look somewhat interesting... XSLC v0.4 is supposed to compile an XSL stylesheet into C++ code for translating XML input, then there's XSLJIT which is supposed to be a just-in-time compiler that produces efficient machine code on the fly to...

Jordi -- Thanks... Don't thing MSXML is going to run on my freeBSD boxes, though. That's why I was looking into a C or C++ library for that purpose. I've found quite a few on the web. The problem is I have no idea which ones are worth a hoot and which are garbage.

msturges -- If I undersdtand what you are trying to do correctly, you are simply looking to display each narrative line in your output. Since the <xsl:for-each> statement has already selected you &quot;Narrative&quot; node, you can not re-select it inside the loop. This, I think, should do...

Okay... I'm about up to my neck in trying to solve all these browser dependent issues with XML/XSLT transforms! I like the idea of leaving the transform to the client as it nicely offloads the processing overhead that the sorting and everything else requires. However, the HUGE issues of trying...

xsl:import should do the trick for you I think... put each template into a separate file and then just import the ones you need only when needed. I hope I understood your question correctly.

A ha! Now I know why the user name and password was not working. For the benefit of those reading over my shoulder... in order for the XSL pages to work in IE 6 within a password protected area, the user much allow cookies from the host web site... even if the site uses no cookies (mine does...

Here's another exmaple of &quot;odd&quot; behavior from Netscape 6 regarding output formatting... The following code fragment is intended to provide a link list at the top of each table in the output to allow the user to jump to one of the other tables. Note that it is supposed to be creating a...

RoadRacer -- I could be mistaken on this, but I believe you can use <xsl:output cdata-section-elements='description' blah blah blah> to solve the problem. If I understand the syntax correctly, that should result in treating all &quot;description&quot; elements in the source data as being...

Okay... on to bigger better problems. I'm having a problem with Netscape 6.2 users and my XSL stylesheets. I make fairly heavy use of <DIV> tags in the transforms and use the &quot;STYLE&quot; attribute of those tags to locate the layouts on the screen (X,Y) and to size them. This works as...

I found the problem... I had both the XML pages and the XSL transforms inside of the member area of the site (password protected) -- It seems that for some users their IE6 borwser would not supply their user name and password to retrieve the XSL page -- thus the access denied problem. So... I...

Codefish -- Thanks for the info (I had already read that thread). The problem is the page contains no special characters and works in just about everyone's IE6 copy I know of except this one person's IE6 he has installed at work. In fact, he was having problems with IE5.5 and the site at home...