Cart
[Home] [By Thread] [By Date] [Recent Entries]
Yves Forkl wrote:
try XSLT, it is an XML language that can be used to describe any desired transformation.
In general, when you need a kind of customization that cannot be handled by parameters, it is common (?) to create a meta-stylesheet which creates a specific stylesheet with all your rules. However, I may not understand fully what you mean. When I need many customizations, I tend to create a settings file in XML and read it in with doc() or document(). The settings file itself can be a result of a transformation. Also, the settings file, once read with document(), can be processed using normal template matching rules. In other situations, I have resorted to list parameters (i.e., having a parameter with a value of "1,12,16,3,4", which can mean the columns to be sorted). Using tokenize() you can easily get your data from them. Optional imports, if that is your primary problem of customization, can be achieved by either carefully looking at precedence rules, or by utilizing the 'use-when' with system properties. The system properties can be set from the host language, giving you even further customization possibilities. Finally, you can think of extension functions like saxon:parse() that take a stylesheet as argument. -- Abel
|
