Using Custom XSLTs

[Ashok Hariharan]

There are some changes regarding using Custom XSLTs . 

These are the XSLT files in the configuration folder under system/transformer/xsl . In some cases you may need to customize these XSLTs , directly editing them is not advisable since they are used by the middleware. 

I have added a way to override-existing or add-new templates via a customization folder. 

For e.g. if we look at the test customization folder : 

http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/

There is new folder within it called "custom" :

http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/custom/

In the "xsl" folder within that - you will find XSL files with the same name as in system/transformer/xsl :

http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/custom/xsl/

• add_an_ns.xsl
• add_bungeni_ns.xsl
• add_rdf_ns.xsl
• cleanup.xsl
• merge_styles.xsl
• meta_language_add_bungeni_ns.xsl
• meta_language_normalization.xsl

However these files are not the same - they dont have any content except an xsl:import statement -- for .e.g. : 

http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/system_configs/xsl/meta_language_normalization.xsl

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
	xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0"
	xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0"
	xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"
	xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0"
	xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0"
	xmlns:fo="urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0"
	xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0"
	xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0"
	xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0"
	xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0"
	xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0"
	xmlns:math="http://www.w3.org/1998/Math/MathML"
	xmlns:form="urn:oasis:names:tc:opendocument:xmlns:form:1.0"
	xmlns:script="urn:oasis:names:tc:opendocument:xmlns:script:1.0"
	xmlns:ooo="http://openoffice.org/2004/office" xmlns:ooow="http://openoffice.org/2004/writer"
	xmlns:oooc="http://openoffice.org/2004/calc" xmlns:dom="http://www.w3.org/2001/xml-events"
	xmlns:xforms="http://www.w3.org/2002/xforms" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:saxon="http://saxon.sf.net/"
        xmlns:field="urn:openoffice:names:experimental:ooo-ms-interop:xmlns:field:1.0"
        xmlns:rpt="http://openoffice.org/2005/report"
        xmlns:anx="http://anx.akomantoso.org/1.0"
        xmlns:of="urn:oasis:names:tc:opendocument:xmlns:of:1.2"
        xmlns:rdfa="http://docs.oasis-open.org/opendocument/meta/rdfa#"
        xmlns:bungeni="http://editor.bungeni.org/1.0/anx/" 
	exclude-result-prefixes="xsl xsd xsi text office style table draw fo xlink dc meta number svg chart dr3d math form script ooo ooow oooc dom xforms field rpt rdfa of anx"
	extension-element-prefixes="saxon" version="2.0">
	
	<xsl:import href="../../system/transformer/xsl/meta_language_normalization.xsl"/>
	
</xsl:stylesheet>

But if you look at the same XSLT in system/transformer/xsl : http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/system_configs/xsl/meta_language_normalization.xsl

its a full fledged XSLT.

So lets say you want to customize one of the templates e.g. :

<xsl:template match="ref">
		<inline name="ref">
			<xsl:attribute name="class" select="tokenize(@name,':')[position()=1]"/>
			<xsl:attribute name="href"
				select="if (tokenize(@name,':')[position()=2]) then tokenize(@name,':')[position()=2] else @href"/>
			<xsl:attribute name="id" select="generate-id(.)"/>
			<xsl:apply-templates/>
		</inline>

	</xsl:template>

in the master XSLT - you just have to redefine it in the same XSLT file provided in "custom/xsl" and the system will pick up your overriden XSL..

Similarly you can add new template matchers in the same file.

Note : this is only for system/transformer/xsl templates - i will shortly support it also for generator templates (system/generator ) 

Ashok