specific content for this page

1) This is indeed a problem of the CDML2XSLT conversion tool: It just inserts the code of the include file for every FMP:Include

In your original CDML code (make a backup copy, of course), remove the FMP:Includes. Convert your cdml files then to XSLT, as well as the include files.

In the include files, change your expression to a named template and remove the match attribute.

E.g.

In the calling files, put immediately after and before the first .

Within , you can place .

You can even pass parameters with xsl:with-param (which must be a child element of xsl:call-template, one xsl:with-param per passed parameter), see e.g. this example

<?xml version="1.0" encoding="UTF-8"?>

<?xslt-cwp-query params="-grammar=fmresultset"?>



  

  

  .

  .

  .

  

  

    

      

        som title

        

        

        

        

      

      

        

          

            --Navigation--

            

              

                    

               

.

.

.

The include file would look like

<?xml version="1.0" encoding="UTF-8"?>



  

  

  

    

.

.

.

One problem you may face is that if there are errors, there is no hint in the error message in which include file the error occured, and you just get a line number. For debugging, you have then to comment out the xsl:call-template statements (with ) and to turn on one after the other to find where the error happens.

It is some manual work, but it is worth the effort and you can build very modular solutions.

2) The images must be placed where your static files reside, i.e. in the root directory or a subdirectory of your web site which are served by the web server software, not into the xslt-template-files folder.

Thanks so much, Martin. I needed to do some minor reconstruction to each page, but the includes are now working.

It took me a lot longer to figure out where to put the graphics (and the css file as well) because I don't have any static pages to put them with. I finally got it, though.