From: G. Ken Holman (gkholman@CraneSoftwrights.com)
Date: Thu Mar 27 2003 - 06:52:45 PST
At 2003-03-27 13:57 +0100, Obenaus, Detlef wrote:
>...
><xsl:import href="./seminar2pdf_cover_front.xsl"/>
><xsl:import href="./seminar2pdf_cover_back.xsl"/>
><xsl:import href="./seminar2pdf_document_info.xsl"/>
><xsl:import href="./seminar2pdf_toc.xsl"/>
><xsl:import href="./seminar2pdf_body.xsl"/>
><xsl:import href="./seminar2pdf_glossary.xsl"/>
><xsl:import href="./seminar2pdf_scripts.xsl"/>
><xsl:import href="./seminar2pdf_styles.xsl"/>
><xsl:import href="./seminar2pdf_translate_en.xsl"/>
>...
>Error at fo:block on line 174 of
>file:/D:/Data/Diet/XSL/Testenviroment/seminar/seminar2pdf_toc.xsl: No
>attribute-set exists named TOCNumber
>...
>The attributes-set exist in seminar2pdf_styles.xsl.
>
>Could you give me a hint!?
All top-level constructs are visible to all fragments after all of the
imported fragments have been assimilated into that which becomes the
running stylesheet.
I would venture that perhaps you have a typographical error (upper
case/lower case?) or a misnamed attribute on the set that is not being
flagged by the processor.
If everything looks kosher, then I would question the conformance of the
XSLT processor ... but I'd rather think it was somewhere hidden in the markup.
Rearranging the fragments will *only* have an effect on like-named
top-level constructs ... if there are none, then the order is irrelevant.
I hope this helps.
............... Ken
-- Upcoming hands-on in-depth XSLT/XPath and/or XSL-FO North America: June 16-20, 2003 G. Ken Holman mailto:gkholman@CraneSoftwrights.com Crane Softwrights Ltd. http://www.CraneSoftwrights.com/f/ Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995) ISBN 0-13-065196-6 Definitive XSLT and XPath ISBN 0-13-140374-5 Definitive XSL-FO ISBN 1-894049-08-X Practical Transformation Using XSLT and XPath ISBN 1-894049-10-1 Practical Formatting Using XSL-FO Male Breast Cancer Awareness http://www.CraneSoftwrights.com/f/bc ------------------- (*) To unsubscribe, send a message with words 'unsubscribe xep-support' in the body of the message to majordomo@renderx.com from the address you are subscribed from. (*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Thu Mar 27 2003 - 06:45:32 PST