Rendering custom XML markup
| |
|
|
Note
|
This topic assumes you have a thorough understanding of XML and XSL syntax.
|
If the HTML code created by Hyper.Net in the TRANSFORMED property for a Topic does not meet your needs, or if you would like to modify it to contain customized markup or if you need to generate a completely different XML, you need to understand the way Hyper.Net transforms rich text content and where you will need to make modifications. Here is how Hyper.Net processes rich text content:
| |
· |
Hyper.Net parses the Word or Word-compatible source document and analyzes its heading-level structure to determine the document's table of contents.
|
| |
· |
Hyper.Net extracts the content within each section within the table of contents and creates a topic for section's content.
|
| |
· |
Hyper.Net transforms the rich text into an intermediate, object-oriented XML representation (as opposed to the page-oriented representation of content provided by Word. This XML is referred to as HNXML.
|
| |
· |
Hyper.Net applies the XSLT defined for the Transformed Format in the document type profile to the HNXML to create the HTML that is stored in the TRANSFORMED property:
|
| |
|
|
Tip
|
You can also designate the XSLT you wish to use in the schema associated with the document type profile. Edit the schema, click on Publication Manipulation in the left navigator, click on XSLT and select the XSLT you wish to use.
| |
|
|
Note
|
If you have specified a value in both places, the value in the schema overrides the value on the document type profile.
|
|
To modify the markup that is generated into the TRANSFORMED property, follow these steps:
| |
|
|
|
Step
|
|
1
|
Go to the folder named xslt found in the HyperNet folder on the file system. You will find the default XSLT hnxml.xslt in this folder.
|
|
2
|
Make a copy of this file and give it a name you will use in your document type profiles. For discussion purposes, let's say the new file is named myxml.xslt.
|
|
3
|
Within the xslt folder you will see a subfolder named default. This folder contains a number of sub-XSLTs used by hnxml.xslt. Make a copy of this folder and give it the same name as your new XSLT, for example: myxml.
|
|
4
|
Open myxml.xslt in a text editor or in Visual Studio. Change the references to the subfolder default to the subfolder myxml.
|
|
5
|
You are now free to modify myxml.xslt and all of the XSLTs in the myxml folder to suit your needs without having to worry about breaking the default XSLTs provided by Hyper.Net.
|
|
6
|
To test your new XSLT, select it for use in the section for the Transformed Format on the document type profile.
|
| |
|
|
Note
|
The HNXML for any given source file is only available during the transformation process. It is deleted along with numerous other temporary files after the transformation process has been completed. If you should need it for further customer processing, you can cause a copy to be generated by modifying the code inside the XSLT associated with the document type profile. Alternatively you could programmatically create a copy on the file system from within the transformer you compile and specify on the document type profile. These are both extremely advanced scenarios. More information is available at www.coextant.com in the Hyper.Net Support Database.
|