forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-368) Add ihtml to "Deprecation of .ehtml and .ihtml" reference
Date Thu, 18 Nov 2004 23:33:50 GMT
The following comment has been added to this issue:

     Author: Clay Leeds
    Created: Thu, 18 Nov 2004 5:33 PM
I got compliance.ihtml to skin (and succeed), using the seed site. I'm still baffled that
the same file doesn't Just Work(tm) with xml-fop.

WAIT A MINUTE! I think I found the answer. I just commented out this file:

    <map:pipeline internal-only="false">
      <!-- ========================== FOP Additions ========================== -->
      <map:match pattern="**compliance.xml">
        <map:generate src="{project:content.xdocs}{1}compliance.xml"/>
          <map:transform src="{project:resources.stylesheets}/compliance2document.xsl"/>
        <map:serialize type="xml"/>
      <!-- ======================== End FOP Additions ======================== -->

This compliance transformation was a throwback to when the plan was to have Forrest/Cocoon
generate the Compliance page using compliance2document.xsl. Because I'm not doing that any
more (I'm 'punting' and just going to generate that file and pass it through as 'ihtml'),
that transformation is no longer needed. This is also why the file processed nicely when in
the seed/.

In fact, removing sitemap.xmap altogether may fix the other problems I was having as well,
since I'm planning on 'manually' copying all *.svg, *.png & *.pdf files myself anyway.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-368
    Summary: Add ihtml to "Deprecation of .ehtml and .ihtml" reference
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Forrest

   Reporter: Clay Leeds

    Created: Fri, 12 Nov 2004 12:30 PM
    Updated: Thu, 18 Nov 2004 5:33 PM

In spite of the title of this section, it doesn't mention .ihtml.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message