> You probably want the first template to be > <xsl:template match="parent-of-employer-and-general-and-employees"> > <fo:flow> > <xsl:apply-templates select="employee"> > ^^^^^^^^^^^^^^^^^^ > ... > See > http://www.w3.org/TR/xslt#built-in-rule > why this is so.
Indeed, this is exactly what I'm thinking... Already thought about this a few weeks ago, but only now does it seem really necessary ( still funny that it produced the desired result on the m$-platform, or does this have to do with the xalan version? ) >> Another weird detail (maybe there's a perfectly valid explanation): although >> the xslt and xml have the "ISO-8859-1" encoding, the resulting .fo is >> "UTF-8"-encoded. > Why do you think this is weird? Read what the spec tells you about > the default output encoding: > http://www.w3.org/TR/xslt#section-XML-Output-Method Didn't know this at all... probably because I haven't used a 'pure' xml/xslt to fo transformation before ( so this was happening all the time, but since I never really paid much attention to the intermediate .fo, I never noticed. ) > For these kind of questions, reagarding pure XSLT, you should ask on > the XSL list: > http://www.mulberrytech.com/xsl/xsl-list/ Again, my thanks for the info! Greetz, Andreas Delmelle ps : Most agree that l-o-v-e is the primary motor in life. Take it from me, the second one is named ... A-p-p-l-e! ( On what machine can one watch a dvd one moment - in less than five seconds ... for the first time -, and a few seconds later edit a tcsh-script with vi? Only on mac, I guess... The future is now! If you ever have some spare cash left & are not sure what to do with it, don't hesitate... ) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
