rpms/saxon/devel saxon.saxonq.script, NONE, 1.1 saxonq.1, NONE, 1.1 .cvsignore, 1.2, 1.3 saxon.1, 1.1, 1.2 saxon.build.script, 1.1, 1.2 saxon.saxon.script, 1.1, 1.2 saxon.spec, 1.5, 1.6 sources, 1.2, 1.3
Lubomir Rintel
lkundrak at fedoraproject.org
Thu Nov 26 17:23:15 UTC 2009
Author: lkundrak
Update of /cvs/pkgs/rpms/saxon/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv30032
Modified Files:
.cvsignore saxon.1 saxon.build.script saxon.saxon.script
saxon.spec sources
Added Files:
saxon.saxonq.script saxonq.1
Log Message:
* Tue Nov 03 2009 Lubomir Rintel <lkundrak at v3.sk> - 9.2.0.3-1
- New package, based on saxon8
--- NEW FILE saxon.saxonq.script ---
#!/bin/sh
#
# saxon script
# JPackage Project <http://www.jpackage.org/>
. /usr/share/java-utils/java-functions
MAIN_CLASS=net.sf.saxon.Query
BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar bea-stax-api.jar bea-stax-ri.jar"
# Optional jars
CLASSPATH="$CLASSPATH:"$(build-classpath docbook-xsl-saxon \
avalon-logkit xml-commons-resolver 2>/dev/null) || :
# If we have resolver, add the CatalogManager.properties dir to CLASSPATH,
# and tweak command line options so that it's used.
args=
if echo "$CLASSPATH" | grep xml-commons-resolver >/dev/null 2>&1 ; then
CLASSPATH="$CLASSPATH:/etc/java/resolver"
# Tune options to use resolver.
r=org.apache.xml.resolver.tools.ResolvingXMLReader
for opt in -x -y ; do
if ! echo $@ | grep "\\$opt " >/dev/null 2>&1 ; then
args="$args $opt $r"
fi
done
r=org.apache.xml.resolver.tools.CatalogResolver
if ! echo $@ | grep "\\-r " >/dev/null 2>&1 ; then
args="$args -r $r"
fi
fi
# Set parameters
set_jvm
set_classpath $BASE_JARS
set_flags $BASE_FLAGS
set_options $BASE_OPTIONS
# Let's start
run $args "$@"
--- NEW FILE saxonq.1 ---
.\" Kudos to: xsltproc(1), help2man,
.\" http://www.saxonica.com/documentation/using-xquery/commandline.html
.TH SAXON8Q "1" "March 2006" "8.7" "User Commands"
.SH NAME
saxon8q \- manual page for saxon8q
.SH SYNOPSIS
.B saxon8q
[\fIoptions\fR] \fIquery \fR[ \fIparams\fR...]
.SH DESCRIPTION
saxon8q runs a query contained in a file.
.SH OPTIONS
The options must come first, then the file name containing the query, then the params.
.TP
The options are as follows (in any order):
.TP
\fB\-cr\fR classname
Use the specified CollectionURIResolver to process collection URIs passed to the collection() function. The CollectionURIResolver is a user\-defined class that implements the net.sf.saxon.CollectionURIResolver interface.
.TP
\fB\-ds\fR
Use the linked tree model for source documents. See Choosing a Tree Model.
.TP
\fB\-dt\fR
Use the tinytree tree model for source documents. This is the default tree model. See Choosing a Tree Model.
.TP
\fB\-e\fR
Display a query execution plan. This is a representation of the expression tree after rewriting by the optimizer.
.TP
\fB\-l\fR
Causes line numbers to be maintained for source documents. These are accessible using the extension function saxon:line\-number(). Line numbers are useful when the purpose of the query is to find errors or anomalies in the source XML file. Without this option, line numbers are available while source documents are being parsed and validated, but they are not retained in the tree representation of the document.
.TP
\fB\-mr\fR classname
Use the specified ModuleURIResolver to process all query module URIs. The ModuleURIResolver is a user\-defined class that implements the net.sf.saxon.query.ModuleURIResolver interface. It is invoked to process URIs used in the import module declaration in the query prolog, and (if \fB\-u\fR is also specified, or if the file name begins with http: or file:) to process the URI of the query source file provided on the command line.
.TP
\fB\-noext\fR
Prevents the query calling external Java functions. This is useful for safety if the query is untrusted.
.TP
\fB\-o\fR filename
Send output to named file. In the absence of this option, the results go to standard output. The output format depends on whether the \fB\-wrap\fR option is present.
.TP
\fB\-p\fR
Use the PTreeURIResolver. This option is available in Saxon\-SA only. It cannot be used in conjunction with the \fB\-r\fR option, and it automatically switches on the \fB\-u\fR and \fB\-sa\fR options. The effect is twofold. Firstly, Saxon\-specific file extensions are recognized in URIs (including the URI of the source document on the command line). Currently the only Saxon\-specific file extension is .ptree, which indicates that the source document is supplied in the form of a Saxon PTree. This is a binary representation of an XML document, designed for speed of loading. Secondly, Saxon\-specific query parameters are recognized in a URI. Currently the only query parameter that is recognized is val. This may take the values strict, lax, or strip. For example, source.xml?validation=strict loads a document with strict schema validation.
.TP
\fB\-pull\fR
Execute query in pull mode. This may give performance advantages for certain kinds of query, especially queries that construct intermediate trees in memory.
.TP
\fB\-r\fR classname
Use the specified URIResolver to process all URIs. The URIResolver is a user\-defined class, that implements the URIResolver interface defined in JAXP, whose function is to take a URI supplied as a string, and return a SAX InputSource. It is invoked to process URIs used in the doc() function, and (if \fB\-u\fR is also specified) to process the URI of the source file provided on the command line.
.TP
\fB\-s\fR filename\-or\-URI
Take input from the specified file. If the \fB\-u\fR option is specified, or if the name begins with file: or http:, then the name is assumed to be a URI rather than a filename. This file must contain an XML document. The document node of the document is made available to the query as the context item. The source document can be specified as \- to take the source from standard input.
.TP
\fB\-sall\fR
Strips all whitespace text nodes from source documents before any further processing, regardless of any xml:space attributes in the source document.
.TP
\fB\-signorable\fR
Strips all ignorable whitespace text nodes from source documents before any further processing, regardless of any xml:space attributes in the source document. Whitespace text nodes are ignorable if they appear in elements defined in the DTD or schema as having element\-only content.
.TP
\fB\-snone\fR
Strips no whitespace before further processing.
.TP
\fB\-strip\fR
Equivalent to \fB\-sall\fR: retained for compatibility.
.TP
\fB\-t\fR
Display version and timing information to the standard error output. The output also traces the files that are read and written, and extension modules that are loaded.
.TP
\fB\-T\fR
Enable execution tracing. This will cause a trace of the query execution to be output to the standard error output. The events that are traced are currently function calls (entry and exit) and element construction.
.TP
\fB\-TJ\fR
Switches on tracing of the binding of calls to external Java methods. This is useful when analyzing why Saxon fails to find a Java method to match an extension function call in the stylesheet, or why it chooses one method over another when several are available.
.TP
\fB\-u\fR
Indicates that the name of the source document is a URI; otherwise it is taken as a filename, unless it starts with http: or file:, in which case they it is taken as a URL.
.TP
\fB\-v\fR
Indicates that source documents are to be parsed using a validating parser (this invokes DTD validation, not schema validation).
.TP
\fB\-val\fR
This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option. It requests strict validation of source documents using an XML Schema.
.TP
\fB\-vlax\fR
This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option. It requests lax validation of source documents using an XML Schema. That is, the document will be validated if a suitable schema is available, and will not be validated otherwise.
.TP
\fB\-vw\fR
Indicates that validation errors found when validating the result tree should be treated as warnings only. This option is available only with the Saxon\-SA version of the command, com.saxonica.Query.
.TP
\fB\-wrap\fR
Wraps the result sequence in an XML element structure that indicates the type of each node or atomic value in the query result. This format can handle any type of query result. In the absence of this option, the command effectively wraps a document{} constructor around the supplied query, so that the result is a single XML document, which is then serialized. This will fail if the query result includes constructs that cannot be added to a document node in this way, notably free\-standing attribute nodes.
.TP
\fB\-1\fR.1
Allow XML 1.1 and XML Namespaces 1.1 constructs. This option must be set if source documents using XML 1.1 are to be read, or if result documents are to be serialized as XML 1.1. This option also enables use of XML 1.1 constructs within the query itself.
.TP
\-?
Display command syntax
.TP
query Identifies the file containing the query. Mandatory. The argument can be specified as \- to read the query from standard input. The query can also be specified inline by enclosing it in curly braces (if it contains spaces, you will also need quotes outside the curly braces to keep the command line processor happy). For example java net.sf.saxon.Query {doc('a.xml')//p[1]} selects elements within the file a.xml in the current directory.
A param takes the form name=value, name being the name of the parameter, and value the value of the parameter. These parameters are accessible within the query as external variables, using the syntax, provided they are declared in the query prolog. If there is no such declaration, the supplied parameter value is silently ignored.
.PP
A param preceded by a leading plus sign (+) is interpreted as a filename or directory. The content of the file is parsed as XML, and the resulting document node is passed to the stylesheet as the value of the parameter. If the parameter value is a directory, then all the immediately contained files are parsed as XML, and the resulting sequence of document nodes is passed as the value of the parameter. For example, +lookup=lookup.xml sets the value of the external variable lookup to the document node at the root of the tree representing the parsed contents of the file lookup.xml.
.PP
A param preceded by a leading exclamation mark is interpreted as a serialization parameter. For example, !indent=yes requests indented output, and !encoding=iso\-8859\-1 requests that the serialized output be in ISO 8859/1 encoding. This is equivalent to specifying the option declaration declare option saxon:output indent=yes; or declare option saxon:output encoding=iso\-8859\-1; in the query prolog.
.PP
Under Windows, and some other operating systems, it is possible to supply a value containing spaces by enclosing it in double quotes, for example name=John Smith. This is a feature of the operating system shell, not something Saxon does, so it may not work the same way under every operating system.
.PP
If the parameter name is in a non\-null namespace, the parameter can be given a value using the syntax {uri}localname=value. Here uri is the namespace URI of the parameter's name, and localname is the local part of the name.
.PP
This applies also to output parameters. For example, you can set the indentation level to 4 by using the parameter !{http://saxon.sf.net/}indent\-spaces=4. For the extended set of output parameters supported by Saxon, see Additional serialization parameters.
.SH AUTHOR
Michael H. Kay <mike at saxonica.com>
Index: .cvsignore
===================================================================
RCS file: /cvs/pkgs/rpms/saxon/devel/.cvsignore,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- .cvsignore 11 Mar 2007 19:43:40 -0000 1.2
+++ .cvsignore 26 Nov 2009 17:23:14 -0000 1.3
@@ -1 +1 @@
-saxon6-5-5.zip
+saxon-resources9-2-0-2.zip
Index: saxon.1
===================================================================
RCS file: /cvs/pkgs/rpms/saxon/devel/saxon.1,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- saxon.1 11 Mar 2007 19:43:40 -0000 1.1
+++ saxon.1 26 Nov 2009 17:23:14 -0000 1.2
@@ -1,135 +1,148 @@
.\" Kudos to: xsltproc(1), help2man,
-.\" http://saxon.sourceforge.net/saxon6.5.5/instant.html
-.TH SAXON "1" "July 2004" "6.5.5" "User Commands"
+.\" http://www.saxonica.com/documentation/using-xsl/commandline.html
+.TH SAXON8 "1" "March 2006" "8.7" "User Commands"
.SH NAME
-saxon \- Process XML documents with XSLT stylesheets
+saxon8 \- manual page for saxon8
.SH SYNOPSIS
-.B saxon
-\fR[\fIoptions\fR] \fIsource-doc \fR[\fIstyle-doc\fR] [{param=value}\fR...]
+.B saxon8
+[\fIoptions\fR] \fIsource-document stylesheet \fR[ \fIparams\fR...]
.SH DESCRIPTION
-saxon is a command line tool for applying XSLT stylesheets to XML
-documents.
-.PP
-It is invoked from the command line with some options, followed by the
-name of the source document to be transformed, followed by the the
-name of the stylesheet to use for the transformation, and finally
-followed by optional XSL parameters.
-.PP
-A parameter takes the form name=value, name being the name of the
-parameter, and value the value of the parameter. These parameters are
-accessible within the stylesheet as normal variables, using the $name
-syntax, provided they are declared using a top-level xsl:param
-element. If there is no such declaration, the supplied parameter value
-is silently ignored. You can specify a parameter value containing
-spaces by enclosing it in double quotes, for example name="John Brown".
+saxon8 applies a given stylesheet to a given source XML document.
+
.SH OPTIONS
+
+For a schema\-aware transformation, specify the option \fB\-sa\fR, or (on the Java platform only) use the alternate entry point com.saxonica.Transform. For more details see Schema\-Aware Transformations.
+.TP
+The options must come first, then the two file names, then the params. The stylesheet is omitted if the \fB\-a\fR option is present.
+.TP
+The options are as follows (in any order):
.TP
\fB\-a\fR
-Use the xml-stylesheet processing instruction in the source document
-to identify the stylesheet to be used. When using this option, the
-style-doc argument should be omitted.
-.SP
-The <?xml-stylesheet?> processing instruction must have a
-pseudo-attribute href that identifies the relative or absolute URL of
-the stylesheet document, and a pseudo-attribute type whose value is
-"text/xml", "application/xml", or "text/xsl". For example:
-
- <?xml-stylesheet type="text/xsl" href="../style3.xsl"?>
-
-Stylesheets embedded within the source document are not
-supported in this release.
+Use the xml\-stylesheet processing instruction in the source document to identify the stylesheet to be used. The stylesheet argument should be omitted.
+.TP
+\fB\-c\fR
+Indicates that the stylesheet argument identifies a compiled stylesheet rather than an XML source stylesheet. The stylesheet must have been previously compiled as described in Compiling a Stylesheet.
+.TP
+\fB\-cr\fR classname
+Use the specified CollectionURIResolver to process collection URIs passed to the collection() function. The CollectionURIResolver is a user\-defined class that implements the net.sf.saxon.CollectionURIResolver interface.
+.TP
+\fB\-ds\fR | \fB\-dt\fR
+Selects the implementation of the internal tree model. \fB\-dt\fR selects the tiny tree model (the default). \fB\-ds\fR selects the linked tree model. See Choosing a tree model.
+.TP
+\fB\-im\fR modename
+Selects the initial mode for the transformation. If this is namespaced, it can be written as {uri}localname
.TP
-\fB\-d\fR\fImodel\fR
-Selects the implementation of the internal tree model. -dt selects the
-"tinytree" model. -ds selects the traditional tree model. The default
-is -dt.
+\fB\-it\fR template
+Selects the initial named template to be executed. If this is namespaced, it can be written as {uri}localname. When this option is used, the source file should be omitted.
.TP
\fB\-l\fR
-Switches line numbering on for the source document. Line numbers are
-accessible through the extension function saxon:line-number(), or from
-a trace listener.
-.TP
-\fB\-m\fR \fIclassname\fR
-Use the specified Emitter to process the output from xsl:message. The
-class must implement the com.icl.saxon.output.Emitter class. This
-interface is similar to a SAX ContentHandler, it takes a stream of
-events to generate output. In general the content of a message is an
-XML fragment. By default the standard XML emitter is used, configured
-to write to the standard error stream, and to include no XML
-declaration. Each message is output as a new document.
+Switches line numbering on for the source document. Line numbers are accessible through the extension function saxon:line\-number(), or from a trace listener.
+.TP
+\fB\-m\fR classname
+Use the specified Emitter to process the output from xsl:message. The class must implement the net.sf.saxon.output.Emitter class. This interface is similar to a SAX ContentHandler, it takes a stream of events to generate output. In general the content of a message is an XML fragment. By default the standard XML emitter is used, configured to write to the standard error stream, and to include no XML declaration. Each message is output as a new document.
.TP
\fB\-noext\fR
-Suppress calls on extension functions, other than system-supplied
-Saxon and EXSLT extension functions. This option is useful when
-loading an untrusted stylesheet, perhaps from a remote site using an
-HTTP URL; it ensures that the stylesheet cannot call Java
-methods and thereby gain privileged access to resources on your
-machine.
-.TP
-\fB\-o\fR \fIfilename\fR
-Send output to named file. In the absence of this option, output goes
-to standard output. The file extension of the output file is used to
-decide the default output method if none is specified.
-.TP
-\fB\-r\fR \fIclassname\fR
-Use the specified URIResolver to process all URIs. The URIResolver is
-a user-defined class, that extends the com.icl.saxon.URIResolver
-class, whose function is to take a URI supplied as a string, and
-return a SAX InputSource. It is invoked to process URIs used in the
-document() function, in the xsl:include and xsl:import elements, and
-(if -u is also specified) to process the URIs of the source file and
-stylesheet file provided on the command line. If xml-commons-resolver
-is available, defaults to org.apache.xml.resolver.tools.CatalogResolver.
+Suppress calls on extension functions, other than system\-supplied Saxon and EXSLT extension functions. This option is useful when loading an untrusted stylesheet, perhaps from a remote site using an http:// URL; it ensures that the stylesheet cannot call Java methods and thereby gain privileged access to resources on your machine.
+.TP
+\fB\-novw\fR
+No version warnings. This suppresses the warning message that is normally issued (as required by the W3C specification) when running an XSLT 2.0 processor against a stylesheet that specifies version=1.0.
+.TP
+\fB\-o\fR filename
+Send output to named file. In the absence of this option, the results go to standard output. If the source argument identifies a directory, this option is mandatory and must also identify a directory; on completion it will contain one output file for each file in the source directory. If the stylesheet writes secondary output files using the xsl:result\-document instruction; this filename acts as the base URI for the href attribute of this instruction. In the absence of this option, secondary output files are written relative to the current working directory.
+.TP
+\fB\-p\fR
+Use the PTreeURIResolver. This option is available in Saxon\-SA only. It cannot be used in conjunction with the \fB\-r\fR option, and it automatically switches on the \fB\-u\fR and \fB\-sa\fR options. The effect is twofold. Firstly, Saxon\-specific file extensions are recognized in URIs (including the URI of the source document on the command line). Currently the only Saxon\-specific file extension is .ptree, which indicates that the source document is supplied in the form of a Saxon PTree. This is a binary representation of an XML document, designed for speed of loading. Secondly, Saxon\-specific query parameters are recognized in a URI. Currently the only query parameter that is recognized is val. This may take the values strict, lax, or strip. For example, source.xml?val=strict loads a document with strict schema validation.
+.TP
+\fB\-r\fR classname
+Use the specified URIResolver to process all URIs. The URIResolver is a user\-defined class, that extends the net.sf.saxon.URIResolver class, whose function is to take a URI supplied as a string, and return a SAX InputSource. It is invoked to process URIs used in the document() function, in the xsl:include and xsl:import elements, and (if \fB\-u\fR is also specified) to process the URIs of the source file and stylesheet file provided on the command line.
+.TP
+\fB\-sa\fR
+Invoke a schema\-aware transformation. Requires Saxon\-SA to be installed.
+.TP
+\fB\-sall\fR
+Strips all whitespace text nodes from source documents before any further processing, regardless of any xsl:strip\-space declarations in the stylesheet, or any xml:space attributes in the source document.
+.TP
+\fB\-signorable\fR
+Strips all ignorable whitespace text nodes from source documents before any further processing, regardless of any xsl:strip\-space declarations in the stylesheet, or any xml:space attributes in the source document. Whitespace text nodes are ignorable if they appear in elements defined in the DTD or schema as having element\-only content.
+.TP
+\fB\-snone\fR
+Strips no whitespace before further processing. (However, whitespace will still be stripped if this is specified in the stylesheet using xsl:strip\-space).
.TP
\fB\-t\fR
-Display version and timing information to the standard error output.
+Display version and timing information to the standard error output. The output also traces the files that are read and writing, and extension modules that are loaded.
.TP
\fB\-T\fR
-Display stylesheet tracing information to the standard error
-output. Also switches line numbering on for the source document.
+Display stylesheet tracing information to the standard error output. This traces execution of each instruction in the stylesheet, so the output can be quite voluminous. Also switches line numbering on for the source document.
+.TP
+\fB\-TJ\fR
+Switches on tracing of the binding of calls to external Java methods. This is useful when analyzing why Saxon fails to find a Java method to match an extension function call in the stylesheet, or why it chooses one method over another when several are available.
.TP
-\fB\-TL\fR \fIclassname\fR
-Run the stylesheet using the specified TraceListener. The classname
-names a user-defined class, which must implement
-com.icl.saxon.trace.TraceListener.
+\fB\-TL\fR classname
+Run the stylesheet using the specified TraceListener. The classname names a user\-defined class, which must implement net.sf.saxon.trace.TraceListener
+.TP
+\fB\-TP\fR
+Run the stylesheet using the TraceListener TimedTraceListener. This creates an output file giving timings for each instruction executed. This output file can subsequently be analyzed to give an execution time profile for the stylesheet. See Performance Analysis.
.TP
\fB\-u\fR
-Indicates that the names of the source document and the style document
-are URLs; otherwise they are taken as filenames, unless they start
-with "http:" or "file:", in which case they are taken as URLs.
-.TP
-\fB\-w\fR\fIlevel\fR
-Indicates the policy for handling recoverable errors in the
-stylesheet: -w0 means recover silently, -w1 means recover after
-writing a warning message to the system error output, -w2 means signal
-the error and do not attempt recovery. (Note, this does not currently
-apply to all errors that the XSLT recommendation describes as
-recoverable). The default is -w1.
-.TP
-\fB\-x\fR \fIclassname\fR
-Use the specified SAX parser for source file and for any files loaded
-using the document() function. The parser must be the fully-qualified
-class name of a Java class that implements the org.xml.sax.Parser or
-org.xml.sax.XMLReader interface. If xml-commons-resolver is available,
-defaults to org.apache.xml.resolver.tools.ResolvingXMLReader.
-.TP
-\fB\-y\fR \fIclassname\fR
-Use the specified SAX parser for all stylesheet files, including any
-loaded using xsl:include or xsl:import. The parser must be the
-fully-qualified class name of a Java class that implements the
-org.xml.sax.Parser or org.xml.sax.XMLReader interface. If
-xml-commons-resolver is available, defaults to
-org.apache.xml.resolver.tools.ResolvingXMLReader.
+Indicates that the names of the source document and the style document are URLs; otherwise they are taken as filenames, unless they start with http: or file:, in which case they are taken as URLs
+.TP
+\fB\-v\fR
+Requests DTD\-based validation of the source file and of any files read using the document() function. Requires an XML parser that supports validation.
+.TP
+\fB\-val\fR
+Requests schema\-based validation of the source file and of any files read using the document() function. This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option.
+.TP
+\fB\-vlax\fR
+This option is available only with Saxon\-SA, and it automatically switches on the \fB\-sa\fR option. It requests lax validation of source documents using an XML Schema. That is, the document will be validated if a suitable schema is available, and will not be validated otherwise.
+.TP
+\fB\-vw\fR
+Indicates that validation errors found when validating the result tree should be treated as warnings only. This option is available only with the Saxon\-SA version of the command, com.saxonica.Transform.
+.TP
+\fB\-w0\fR, w1, or w2
+Indicates the policy for handling recoverable errors in the stylesheet: w0 means recover silently, w1 means recover after writing a warning message to the system error output, w2 means signal the error and do not attempt recovery. (Note, this does not currently apply to all errors that the XSLT recommendation describes as recoverable). The default is w1.
+.TP
+\fB\-x\fR classname
+Use specified SAX parser for source file and any files loaded using the document() function. The parser must be the fully\-qualified class name of a Java class that implements the org.xml.sax.Parser or org.xml.sax.XMLReader interface
+.TP
+\fB\-y\fR classname
+Use specified SAX parser for stylesheet file, including any loaded using xsl:include or xsl:import. The parser must be the fully\-qualified class name of a Java class that implements the org.xml.sax.Parser or org.xml.sax.XMLReader interface
+.TP
+\fB\-1\fR.1
+Allow XML 1.1 and XML Namespaces 1.1 constructs. This option must be set if source documents using XML 1.1 are to be read, or if result documents are to be serialized as XML 1.1. This option also enables use of XML 1.1 constructs within the stylesheet itself.
+.TP
+\-?
+Display command syntax
+.TP
+source\-document
+Identifies the source file or directory. Mandatory. If this is a directory, all the files in the directory will be processed individually. In this case the \fB\-o\fR option is mandatory, and must also identify a directory, to contain the corresponding output files. A directory must be specified as a filename, not as a URL. The source\-document can be specified as \- to take the source from standard input.
+.TP
+stylesheet
+Identifies the stylesheet. Mandatory unless the \fB\-a\fR option is used. If the \fB\-c\fR option is used, this argument identifies a compiled stylesheet. The stylesheet argument can be specified as \- to read the stylesheet from standard input.
+
+A param takes the form name=value, name being the name of the parameter, and value the value of the parameter. These parameters are accessible within the stylesheet as normal variables, using the syntax, provided they are declared using a top\-level xsl:param element. If there is no such declaration, the supplied parameter value is silently ignored. If the xsl:param element has an as attribute indicating the required type, then the string value supplied on the command line is cast to this type: this may result in an error, for example if an integer is required and the supplied value cannot be converted to an integer.
+.TP
+A param preceded by a leading exclamation mark (!) is interpreted as an output parameter. For example, !indent=yes requests indented output. This is equivalent to specifying the attribute indent=yes on an xsl:output declaration in the stylesheet. An output parameter specified on the command line overrides one specified within the stylesheet.
+.TP
+A param preceded by a leading plus sign (+) is interpreted as a filename or directory. The content of the file is parsed as XML, and the resulting document node is passed to the stylesheet as the value of the parameter. If the parameter value is a directory, then all the immediately contained files are parsed as XML, and the resulting sequence of document nodes is passed as the value of the parameter. For example, +lookup=lookup.xml sets the value of the stylesheet parameter lookup to the document node at the root of the tree representing the parsed contents of the file lookup.xml.
+.TP
+Under Windows, and some other operating systems, it is possible to supply a value containing spaces by enclosing it in double quotes, for example name=John Smith. This is a feature of the operating system shell, not something Saxon does, so it may not work the same way under every operating system. (In the jEdit console plugin it has to be written as name=John Smith)
+.TP
+If the parameter name is in a non\-null namespace, the parameter can be given a value using the syntax {uri}localname=value. Here uri is the namespace URI of the parameter's name, and localname is the local part of the name.
+.TP
+This applies also to output parameters. For example, you can set the indentation level to 4 by using the parameter !{http://saxon.sf.net/}indent\-spaces=4. See also Additional attributes for xsl:output.
+.TP
+If the \fB\-a\fR option is used, the name of the stylesheet is omitted. The source document must contain a <?xml\-stylesheet?> processing instruction before the first element start tag; this processing instruction must have a pseudo\-attribute href that identifies the relative or absolute URL of the stylsheet document, and a pseudo\-attribute type whose value is text/xml, application/xml, or text/xsl. For example:
+.TP
+<?xml\-stylesheet type=text/xsl href=../style3.xsl ?>
.TP
-\fB\-?\fR
-Display command syntax.
+It is also possible to refer to a stylesheet embedded within the source document, provided it has an id attribute and the id attribute is declared in the DTD as being of type ID.
.SH FILES
-.B __RESOLVERDIR__/CatalogManager.properties
+.B /etc/java/resolver/CatalogManager.properties
.RS
The central catalog manager configuration file used by \fBsaxon\fR
for resolving XML entities and URIs if xml-commons-resolver is
available.
.SH "SEE ALSO"
.BR xsltproc (1)
-.SH AUTHOR
+.SH AUTHOR
Michael H. Kay <mike at saxonica.com>
Index: saxon.build.script
===================================================================
RCS file: /cvs/pkgs/rpms/saxon/devel/saxon.build.script,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- saxon.build.script 11 Mar 2007 19:43:40 -0000 1.1
+++ saxon.build.script 26 Nov 2009 17:23:14 -0000 1.2
@@ -24,7 +24,7 @@
<mkdir dir="${build.lib}"/>
<mkdir dir="${build.doc}"/>
<copy todir="${src}">
- <fileset dir="." includes="com/**,org/**"/>
+ <fileset dir="." includes="com/**,org/**,net/**"/>
</copy>
</target>
@@ -40,30 +40,12 @@
</target>
<!-- Build jar archives -->
+
<target name="jar" depends="classes">
- <!-- aelfred -->
- <jar destfile="${build.lib}/${name}-aelfred.jar"
- basedir="${build.classes}"
- includes="com/icl/saxon/aelfred/*">
- <metainf dir="META-INF"
- includes="services/javax.xml.parsers.*" />
- </jar>
- <!-- fop -->
- <jar destfile="${build.lib}/${name}-fop.jar"
- basedir="${build.classes}"
- includes="com/icl/saxon/fop/*"/>
- <!-- jdom -->
- <jar destfile="${build.lib}/${name}-jdom.jar"
- basedir="${build.classes}"
- includes="com/icl/saxon/jdom/*"/>
- <!-- main -->
<jar jarfile="${build.lib}/${name}.jar"
- basedir="${build.classes}"
- excludes="com/icl/saxon/fop/,com/icl/saxon/jdom/,com/icl/saxon/aelfred/">
- <metainf dir="META-INF"
- includes="services/javax.xml.transform.*" />
+ basedir="${build.classes}">
<manifest>
- <attribute name="Main-Class" value="com.icl.saxon.StyleSheet" />
+ <attribute name="Main-Class" value="net.sf.saxon.Transform" />
</manifest>
</jar>
</target>
@@ -77,7 +59,7 @@
package="true"
author="true"
version="true"
- packagenames="com.icl.saxon.*,org.w3c.xsl.*"
+ packagenames="net.sf.saxon.*,org.w3c.xsl.*"
>
<link href="${j2se.javadoc}"/>
<link href="${jdom.javadoc}"/>
Index: saxon.saxon.script
===================================================================
RCS file: /cvs/pkgs/rpms/saxon/devel/saxon.saxon.script,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- saxon.saxon.script 11 Mar 2007 19:43:40 -0000 1.1
+++ saxon.saxon.script 26 Nov 2009 17:23:15 -0000 1.2
@@ -5,19 +5,19 @@
. /usr/share/java-utils/java-functions
-MAIN_CLASS=com.icl.saxon.StyleSheet
+MAIN_CLASS=net.sf.saxon.Transform
-BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar"
+BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar bea-stax-api.jar bea-stax-ri.jar"
# Optional jars
-CLASSPATH="$CLASSPATH:"$(build-classpath docbook-xsl-saxon saxon-fop \
+CLASSPATH="$CLASSPATH:"$(build-classpath docbook-xsl-saxon \
avalon-logkit xml-commons-resolver 2>/dev/null) || :
# If we have resolver, add the CatalogManager.properties dir to CLASSPATH,
# and tweak command line options so that it's used.
args=
if echo "$CLASSPATH" | grep xml-commons-resolver >/dev/null 2>&1 ; then
- CLASSPATH="$CLASSPATH:__RESOLVERDIR__"
+ CLASSPATH="$CLASSPATH:/etc/java/resolver"
# Tune options to use resolver.
r=org.apache.xml.resolver.tools.ResolvingXMLReader
for opt in -x -y ; do
Index: saxon.spec
===================================================================
RCS file: /cvs/pkgs/rpms/saxon/devel/saxon.spec,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- saxon.spec 27 Jul 2009 03:49:00 -0000 1.5
+++ saxon.spec 26 Nov 2009 17:23:15 -0000 1.6
@@ -28,63 +28,60 @@
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
-%define resolverdir %{_sysconfdir}/java/resolver
-
-Summary: Java XSLT processor
+Summary: Java XPath, XSLT 2.0 and XQuery implementation
Name: saxon
-Version: 6.5.5
-Release: 3.3%{?dist}
-Epoch: 0
-License: MPLv1.0
-Group: Text Processing/Markup/XML
+Version: 9.2.0.3
+Release: 1%{?dist}
+# net.sf.saxon.om.XMLChar is from ASL-licensed Xerces
+License: MPLv1.0 and ASL 1.1
+Group: Applications/Text
URL: http://saxon.sourceforge.net/
-Source0: http://download.sf.net/saxon/saxon6-5-5.zip
+Source0: http://dl.sourceforge.net/project/saxon/Saxon-HE/9.2/saxon-resources9-2-0-2.zip
Source1: %{name}.saxon.script
-Source2: %{name}.build.script
-Source3: %{name}.1
+Source2: %{name}.saxonq.script
+Source3: %{name}.build.script
+Source4: %{name}.1
+Source5: %{name}q.1
+# There's no 9.2.0.3 resource bundle, we patch 9.2.0.2 with difference against 9.2.0.3 source bundle
+Patch0: saxon-9.2.0.2-9.2.0.3.patch
+BuildRequires: unzip
+BuildRequires: ant
BuildRequires: jpackage-utils >= 0:1.6
+BuildRequires: bea-stax-api
BuildRequires: xml-commons-apis
-BuildRequires: jdom >= 0:1.0
-BuildRequires: ant
-Requires: xml-commons-apis
-Requires: jpackage-utils >= 0:1.6
-Requires: jdom >= 0:1.0
-
+BuildRequires: xom
+BuildRequires: jdom >= 0:1.0-0.b7
+BuildRequires: java-javadoc
+BuildRequires: jdom-javadoc >= 0:1.0-0.b9.3jpp
+BuildRequires: dom4j
+Requires: jpackage-utils
+Requires: bea-stax-api
+Requires: bea-stax
Requires: jaxp_parser_impl
Requires: /usr/sbin/update-alternatives
-Provides: jaxp_transform_impl
+Provides: jaxp_transform_impl = %{version}-%{release}
+
+# Older versions were split into multile packages
+Obsoletes: %{name}-xpath < %{version}-%{release}
+Obsoletes: %{name}-xom < %{version}-%{release}
+Obsoletes: %{name}-sql < %{version}-%{release}
+Obsoletes: %{name}-jdom < %{version}-%{release}
+Obsoletes: %{name}-dom < %{version}-%{release}
+
BuildArch: noarch
-BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)
%description
-The SAXON package is a collection of tools for processing XML documents.
-The main components are:
-- An XSLT processor, which implements the Version 1.0 XSLT and XPath
- Recommendations from the World Wide Web Consortium, found at
- http://www.w3.org/TR/1999/REC-xslt-19991116 and
- http://www.w3.org/TR/1999/REC-xpath-19991116 with a number of powerful
- extensions. This version of Saxon also includes many of the new features
- defined in the XSLT 1.1 working draft, but for conformance and portability
- reasons these are not available if the stylesheet header specifies
- version="1.0".
-- A Java library, which supports a similar processing model to XSL, but allows
- full programming capability, which you need if you want to perform complex
- processing of the data or to access external services such as a relational
- database.
-So you can use SAXON with any SAX-compliant XML parser by writing XSLT
-stylesheets, by writing Java applications, or by any combination of the two.
-
-%package aelfred
-Summary: Java XML parser
-Group: Text Processing/Markup/XML
-Requires: xml-commons-apis
+Saxon HE is Saxonica's non-schema-aware implementation of the XPath 2.0,
+XSLT 2.0, and XQuery 1.0 specifications aligned with the W3C Candidate
+Recommendation published on 3 November 2005. It is a complete and
+conformant implementation, providing all the mandatory features of
+those specifications and nearly all the optional features.
-%description aelfred
-A slightly improved version of the AElfred Java XML parser from Microstar.
%package manual
Summary: Manual for %{name}
-Group: Documentation
+Group: Applications/Text
%description manual
Manual for %{name}.
@@ -92,36 +89,23 @@ Manual for %{name}.
%package javadoc
Summary: Javadoc for %{name}
Group: Documentation
-BuildRequires: java-javadoc
-BuildRequires: jdom-javadoc >= 0:1.0
-Requires: java-javadoc
-Requires: jdom-javadoc >= 0:1.0
%description javadoc
Javadoc for %{name}.
%package demo
Summary: Demos for %{name}
-Group: Text Processing/Markup/XML
-Requires: %{name} = %{epoch}:%{version}-%{release}
+Group: Applications/Text
+Requires: %{name} = %{version}-%{release}
%description demo
Demonstrations and samples for %{name}.
-%package jdom
-Summary: JDOM support for %{name}
-Group: Text Processing/Markup/XML
-Requires: %{name} = %{epoch}:%{version}-%{release}
-Requires: jdom >= 0:1.0
-
-%description jdom
-JDOM support for %{name}.
-
%package scripts
Summary: Utility scripts for %{name}
-Group: Text Processing/Markup/XML
-Requires: jpackage-utils >= 0:1.6
-Requires: %{name} = %{epoch}:%{version}-%{release}
+Group: Applications/Text
+Requires: jpackage-utils >= 0:1.5
+Requires: %{name} = %{version}-%{release}
%description scripts
Utility scripts for %{name}.
@@ -129,38 +113,51 @@ Utility scripts for %{name}.
%prep
%setup -q -c
-unzip -q source.zip
-cp -p %{SOURCE2} ./build.xml
+unzip -q source.zip -d src
+cd src
+%patch0 -p1 -b .9.2.0.3
+cd ..
+
+cp -p %{SOURCE3} ./build.xml
+
+# deadNET
+rm -rf src/net/sf/saxon/dotnet
+
+# Depends on XQJ (javax.xml.xquery)
+rm -rf src/net/sf/saxon/xqj
+
+# This requires a EE edition feature (com.saxonica.xsltextn)
+rm -rf src/net/sf/saxon/option/sql/SQLElementFactory.java
+
# cleanup unnecessary stuff we'll build ourselves
-rm -rf *.jar docs/api
+rm -rf docs/api
+find . \( -name "*.jar" -name "*.pyc" \) -delete
%build
-export CLASSPATH=%(build-classpath xml-commons-apis jdom)
+mkdir -p build/classes
+cat >build/classes/edition.properties <<EOF
+config=net.sf.saxon.Configuration
+platform=net.sf.saxon.java.JavaPlatform
+EOF
+
+export CLASSPATH=%(build-classpath xml-commons-apis jdom xom bea-stax-api dom4j)
ant \
-Dj2se.javadoc=%{_javadocdir}/java \
-Djdom.javadoc=%{_javadocdir}/jdom
+
%install
rm -rf $RPM_BUILD_ROOT
# jars
mkdir -p $RPM_BUILD_ROOT%{_javadir}
cp -p build/lib/%{name}.jar $RPM_BUILD_ROOT%{_javadir}/%{name}-%{version}.jar
-
-cp -p build/lib/%{name}-aelfred.jar \
- $RPM_BUILD_ROOT%{_javadir}/%{name}-aelfred-%{version}.jar
-
-cp -p build/lib/%{name}-jdom.jar \
- $RPM_BUILD_ROOT%{_javadir}/%{name}-jdom-%{version}.jar
-
-(cd $RPM_BUILD_ROOT%{_javadir} && for jar in *-%{version}*; do \
- ln -sf ${jar} `echo $jar| sed "s|-%{version}||g"`; done)
+ln -s %{name}-%{version}.jar $RPM_BUILD_ROOT%{_javadir}/%{name}.jar
# javadoc
mkdir -p $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version}
cp -pr build/api/* $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version}
-ln -s %{name}-%{version} $RPM_BUILD_ROOT%{_javadocdir}/%{name}
# demo
mkdir -p $RPM_BUILD_ROOT%{_datadir}/%{name}
@@ -168,24 +165,21 @@ cp -pr samples/* $RPM_BUILD_ROOT%{_datad
# scripts
mkdir -p $RPM_BUILD_ROOT%{_bindir}
-sed 's,__RESOLVERDIR__,%{resolverdir},' < %{SOURCE1} \
- > $RPM_BUILD_ROOT%{_bindir}/%{name}
+install -p -m755 %{SOURCE1} $RPM_BUILD_ROOT%{_bindir}/%{name}
+install -p -m755 %{SOURCE2} $RPM_BUILD_ROOT%{_bindir}/%{name}q
mkdir -p $RPM_BUILD_ROOT%{_mandir}/man1
-sed 's,__RESOLVERDIR__,%{resolverdir},' < %{SOURCE3} \
- > $RPM_BUILD_ROOT%{_mandir}/man1/%{name}.1
+install -p -m644 %{SOURCE4} $RPM_BUILD_ROOT%{_mandir}/man1/%{name}.1
+install -p -m644 %{SOURCE5} $RPM_BUILD_ROOT%{_mandir}/man1/%{name}q.1
# jaxp_transform_impl ghost symlink
ln -s %{_sysconfdir}/alternatives \
$RPM_BUILD_ROOT%{_javadir}/jaxp_transform_impl.jar
-# fix newlines in docs
-for i in doc/*.html; do
- tr -d \\r < $i > temp_file.html; mv temp_file.html $i
-done
%clean
rm -rf $RPM_BUILD_ROOT
+
%post
update-alternatives --install %{_javadir}/jaxp_transform_impl.jar \
jaxp_transform_impl %{_javadir}/%{name}.jar 25
@@ -197,57 +191,51 @@ update-alternatives --install %{_javadir
} >/dev/null 2>&1 || :
%files
-%defattr(0644,root,root,0755)
+%defattr(-,root,root,-)
%{_javadir}/%{name}.jar
%{_javadir}/%{name}-%{version}.jar
%ghost %{_javadir}/jaxp_transform_impl.jar
-%files aelfred
-%defattr(0644,root,root,0755)
-%{_javadir}/%{name}-aelfred*
-
-%files jdom
-%defattr(0644,root,root,0755)
-%{_javadir}/%{name}-jdom*
-
%files manual
-%defattr(0644,root,root,0755)
+%defattr(-,root,root,-)
%doc doc/*.html
%files javadoc
-%defattr(0644,root,root,0755)
-%doc %{_javadocdir}/*
+%defattr(-,root,root,-)
+%doc %{_javadocdir}/%{name}-%{version}
%files demo
-%defattr(0644,root,root,0755)
+%defattr(-,root,root,-)
%{_datadir}/%{name}
+%exclude %{_datadir}/%{name}/scm/scmschema.xsd.bak
%files scripts
-%defattr(0755,root,root,0755)
+%defattr(-,root,root,-)
%{_bindir}/%{name}
-%attr(0644,root,root) %{_mandir}/man1/%{name}.1*
+%{_bindir}/%{name}q
+%{_mandir}/man1/%{name}.1*
+%{_mandir}/man1/%{name}q.1*
-%changelog
-* Sun Jul 26 2009 Fedora Release Engineering <rel-eng at lists.fedoraproject.org> - 0:6.5.5-3.3
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild
-* Wed Feb 25 2009 Fedora Release Engineering <rel-eng at lists.fedoraproject.org> - 0:6.5.5-2.3
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
+%changelog
+* Tue Nov 03 2009 Lubomir Rintel <lkundrak at v3.sk> - 9.2.0.3-1
+- New package, based on saxon8
-* Thu Jul 10 2008 Tom "spot" Callaway <tcallawa at redhat.com> - 0:6.5.5-1.3
-- drop repotag
-- fix license tag
-
-* Sun Mar 11 2007 Vivek Lakshmanan <vivekl at redhat.com> - 0:6.5.5-1jpp.2.fc7
-- First build for Fedora
-- Resolves: #227114 (Missing BR on ant - Thanks mcepl)
-
-* Wed Feb 14 2007 Deepak Bhole <dbhole at redhat.com> - 0:6.5.5-1jpp.1
-- Update to 6.5.5
-- Fix per Fedora guidelines
+* Tue Nov 03 2009 Lubomir Rintel <lkundrak at v3.sk> - 0:8.7-1
+- Tidied up for Fedora
-* Tue May 02 2006 Ralph Apel <r.apel at r-apel.de> - 0:6.5.3-4jpp
-- First JPP-1.7 release
+* Tue Mar 14 2006 Deepak Bhole <dbhole at redhat.com> - 0:B.8.7-1jpp
+- Changed package name for compatibility
+- Upgraded to 8.7
+- Added saxonq script for queries
+- Updated man pages
+
+* Mon Jan 30 2006 Ralph Apel <r.apel at r-apel.de> - 0:8.6.1-1jpp
+- Derive saxonb8 from saxon7
+
+* Mon Sep 05 2005 Ralph Apel <r.apel at r-apel.de> - 0:7.9.1-1jpp
+- Derive saxon7 from saxon
+- no more aelfred nor fop subpackages
* Fri Sep 03 2004 Fernando Nasser <fnasser at redhat.com> - 0:6.5.3-3jpp
- Rebuilt with Ant 1.6.2
Index: sources
===================================================================
RCS file: /cvs/pkgs/rpms/saxon/devel/sources,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- sources 11 Mar 2007 19:43:40 -0000 1.2
+++ sources 26 Nov 2009 17:23:15 -0000 1.3
@@ -1 +1 @@
-e913002af9c6bbb4c4361ff41baac3af saxon6-5-5.zip
+e3da428de3bc37bffebbe4249189f63e saxon-resources9-2-0-2.zip
More information about the scm-commits
mailing list