Unable to open pages after decompiling chm

Feb 17, 2010 at 9:30 PM
Edited Feb 17, 2010 at 9:32 PM

Hi

I need to get this export working on a website rather than as a chm help file
I can decompile the chm using different tools but I keep getting a "page not found" error

Looks like the href markup in the xlst files are causing the problem
After I changed all code to use ../ to go one step down the folder rather than using just the <slash< meaning the root of the webapplication - this is not an issue in the compiled help file and the changes is also working

eg (host.xslt)

<xsl:for-each select="BizTalkBaseObject/HostedReceiveLocations/ReceiveLocation">
    <tr>
        <td></td>
        <td><IMG SRC='../ReceivePortSmall.jpg' VALIGN="center" width="16" height="16"/></td>
        <td>
            <xsl:element name="A">
        <xsl:attribute name="CLASS">TableData</xsl:attribute>
        <xsl:attribute name="HREF">../ReceivePort/<xsl:value-of select="Id" />.htm</xsl:attribute>
        <xsl:value-of select="Name" />
          </xsl:element>
      </td>
    </tr>
</xsl:for-each>

and not this as we have atm

<xsl:for-each select="BizTalkBaseObject/HostedReceiveLocations/ReceiveLocation">
    <tr>
        <td></td>
        <td><IMG SRC='../ReceivePortSmall.jpg' VALIGN="center" width="16" height="16"/></td>
        <td>
            <xsl:element name="A">
        <xsl:attribute name="CLASS">TableData</xsl:attribute>
        <xsl:attribute name="HREF">/ReceivePort/<xsl:value-of select="Id" />.htm</xsl:attribute>
        <xsl:value-of select="Name" />
          </xsl:element>
      </td>
    </tr>
</xsl:for-each>

Thanks /Peter
Developer
Feb 18, 2010 at 12:04 PM

Hi Peter,

Thank you for pointing this issue out. Seems like a really cool idea to have this on a  website.  In the next version we are making stuff pluggable so it should be possible to write a "Website Publisher" that unpacks the info into a folder structure suitable for rendering in a website.

Currently, when we produce the CHM, the artifact info is unpacked into a temp folder and the structure of the CHM is more or less reflected in the folder layout and this is used to compile the help file. I'll test out your changes and see if it can be incorporated into the core code. 

Couple of questions to help prioritise the work

  1. Are you happy with the changed code you are using now and is it important to have the official code base reflecting your change (if it doesnt break the CHM it shouldnt matter if i change the code as you have shown, but just good to know if this is important)
  2. Would it be useful for you if we left the temp folder untouched instead of deleting it (maybe with an option on the UI for this) and you could use the raw info to build your website ? Or are you ok to continue decompiling the CHM?

Cheers

Benjy

 

Feb 18, 2010 at 12:20 PM

No worries

I have messed around with the sourcecode to suit my needs and it's fine :-)

I have also a couple of tiny patch suggestions I'll upload this weekend
eg extending the hhp project file to build full text search - already tested and it seems to work well

Thanks /Peter