Hello Curtney, I would recommend the same as Barry. I also use http://www.w3schools.com/xsl/xsl_languages.asp a lot. I learned xslt by doing it, but I was lucky to have a xslt guru nearby. I would recommend to post some code and then we can tell you which step you missed. Most xsl code is deadly simple if you keep your templates small and think in trees. Try to avoid long xpath queries in match attributes. The underlying xml is a tree of nodes. Matching a node in your xml will move the view on your tree to that node as root node. Your "compiled" xsl's templates (imported/included) are in a tree structure. You only have to understand which templates get precedence over others. Eg. The xsl:include gives all xsl:templates in both files the same precedence (same level in the xsl stylesheet tree structure). The xsl parser tries to find the first matching xsl;template from top to bottom. With xsl:import the xsl stylesheet which contains the import-statement has the preferred templates. If there is no match then the imported xsl stylesheet is consulted. So the imported stylesheet is a child of the other stylesheet in the xsl:stylesheet tree structure.
Nico ----------------------------------------------------------------- Nearly every man who develops an idea works at it up to the point where it looks impossible, and then gets discouraged. that's not the place to become discouraged. > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Barry van Oven > Verzonden: woensdag 4 augustus 2004 22:19 > Aan: [EMAIL PROTECTED] > Onderwerp: RE: Modifying x2html.xsl does not change resulting xhtml > > > Two titles by Wrox Press come to mind (probably because my > wife did the technical review on both :-) ): > > - XSLT Programmer's Reference (2nd Edition) > - Beginning XSLT > > The first is a true reference, handy when you just need to > lookup syntax. > The second is one of the easiest to understand introductions > to XSLT, especially so because it tackles various seeming > idiocsyncrasies most programmers seem to have problems with. > My favorite is: don't iterate, recurse! > > }-----Original Message----- > }From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > }On Behalf Of Curtney Jacobs > }Sent: Wednesday, August 04, 2004 9:35 PM > }To: [EMAIL PROTECTED] > }Subject: Re: Modifying x2html.xsl does not change resulting > xhtml } } }Greetings! > } > }Thanks Michiel, Barry for responding. I don't have a > thorough }understanding of }xslt either and I have been > mostly using various web tutorials }to guide me. I }thought > xslt is something that I can get up to speed with real }quick > but I }was wrong. I need to inverst in a good book. Do you > guys have any }suggestions on a good XSLT book? > } > }So, before I start posting xslt code, let me get a better > }understanding, so I }can ask more intelligible questions ;-) > } }Curtney } } } }On Wednesday 04 August 2004 08:55 am, Barry > van Oven wrote: > }> Curtney, why not post your XSLT and generated XML, so we > can }take a look at }> it? > }> > }> }-----Original Message----- > }> }From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] }> }On Behalf Of Michiel > Meeuwissen }> }Sent: Wednesday, August 04, 2004 9:16 AM }> > }To: [EMAIL PROTECTED] }> }Subject: Re: Modifying x2html.xsl > does not change resulting xhtml }> } }> }Curtney Jacobs > <[EMAIL PROTECTED]> wrote: > }> }> I followed the formatter.jsp example. I created a > second }> }style sheet that }> }> imports the xs/2xhtml.xslt > style sheet. However, whenever }I apply a }> }> formatting to > a field in the second style sheet, all }> }subsequent > formatting }> }> declared in 2xhtml.xslt (first style sheet) is gone. > }> }> > }> }> For example, if a field had any embeded links in a }> > }paragraph then it }> }> disappears. Only the most current > formatting is shown. I am }> }aware that }> }> imported > stylesheets have lower precedence, but I think it }> }is I > that is doing }> }> something wrong. I just don't know what. > }> }> > }> }> I hope this make sense :-( > }> } > }> }Hardly. I think that your problem might be XSL, which is > }> }indeed not a very }> }easy language. It is not cascading > or so, if you override a }> }template the one }> }in the > overridden style sheet is hidden and unused. If you }> }still > need its }> }functionality, you need to copy it in the hiding > template. I }> }think that e.g. > }> }finding links is done in seperate templates, so you > should }> }call these also }> }in your extension. > }> } > }> }But of course, I'm only guessing about what you try, and > I'm }> }no XSLT expert }> }either. Do you have a good book about it? > }> } > }> } Michiel > }> } > }> }-- > }> }Michiel Meeuwissen > }> }Mediacentrum 140 H'sum > }> }+31 (0)35 6772979 > }> }nl_NL eo_XX en_US > }> }mihxil' > }> } [] () > }> } > } > >
