Hello community,

here is the log from the commit of package saxon9 for openSUSE:Factory checked 
in at 2013-01-03 13:48:04
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/saxon9 (Old)
 and      /work/SRC/openSUSE:Factory/.saxon9.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "saxon9", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/saxon9/saxon9.changes    2012-11-30 
12:31:05.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.saxon9.new/saxon9.changes       2013-01-03 
13:48:08.000000000 +0100
@@ -1,0 +2,7 @@
+Fri Dec 21 21:45:46 UTC 2012 - [email protected]
+
+- Replace unmaintained options in man pages with links to website
+- Fix command line flag syntax -foo bar -> -foo:bar
+- Don't use CatalogResolver unless CatalogManager.properties exists
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------



++++++ saxon9.1 ++++++
--- /var/tmp/diff_new_pack.YLQ0zP/_old  2013-01-03 13:48:10.000000000 +0100
+++ /var/tmp/diff_new_pack.YLQ0zP/_new  2013-01-03 13:48:10.000000000 +0100
@@ -1,141 +1,17 @@
-.\" Kudos to: xsltproc(1), help2man,
-.\" http://www.saxonica.com/documentation/using-xsl/commandline.html
-.TH SAXON9 "1" "March 2006" "9.4" "User Commands"
+.TH SAXON9 "1" "December 2012" "9.4" "User Commands"
 .SH NAME
-saxon9 \- manual page for saxon9 
+saxon9 \- Saxon XSLT 2.0 processor
 .SH SYNOPSIS
 .B saxon9
-[\fIoptions\fR] \fIsource-document stylesheet \fR[ \fIparams\fR...]
+[\fIoptions\fR] \fI-s:source-document -xsl:stylesheet \fR[ 
\fIparam=value\fR...]
 .SH DESCRIPTION
 saxon9 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.
+See:
 .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.
+\fIhttp://www.saxonica.com/documentation/using-xsl/commandline.xml\fR
 .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. 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\-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 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\-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. 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. 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 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\-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
-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.
+for command line usage.
 .SH FILES
 .B /etc/java/resolver/CatalogManager.properties
 .RS
@@ -143,6 +19,7 @@
 for resolving XML entities and URIs if xml-commons-resolver is
 available.
 .SH "SEE ALSO"
-.BR xsltproc (1)
+.BR saxon9q (1) ,
+.BR xsltproc (1) .
 .SH AUTHOR 
 Michael H. Kay <[email protected]>

++++++ saxon9.saxon.script ++++++
--- /var/tmp/diff_new_pack.YLQ0zP/_old  2013-01-03 13:48:10.000000000 +0100
+++ /var/tmp/diff_new_pack.YLQ0zP/_new  2013-01-03 13:48:10.000000000 +0100
@@ -16,18 +16,18 @@
 # 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
+if echo "$CLASSPATH" | grep xml-commons-resolver >/dev/null 2>&1 && test -r 
/etc/java/resolver/CatalogManager.properties; 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"
+    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"
+  if ! echo $@ | grep "\\-r:" >/dev/null 2>&1 ; then
+    args="$args -r:$r"
   fi
 fi
 

++++++ saxon9.saxonq.script ++++++
--- /var/tmp/diff_new_pack.YLQ0zP/_old  2013-01-03 13:48:10.000000000 +0100
+++ /var/tmp/diff_new_pack.YLQ0zP/_new  2013-01-03 13:48:10.000000000 +0100
@@ -16,18 +16,18 @@
 # 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
+if echo "$CLASSPATH" | grep xml-commons-resolver >/dev/null 2>&1 && test -r 
/etc/java/resolver/CatalogManager.properties; 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"
+    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"
+  if ! echo $@ | grep "\\-r:" >/dev/null 2>&1 ; then
+    args="$args -r:$r"
   fi
 fi
 

++++++ saxon9q.1 ++++++
--- /var/tmp/diff_new_pack.YLQ0zP/_old  2013-01-03 13:48:10.000000000 +0100
+++ /var/tmp/diff_new_pack.YLQ0zP/_new  2013-01-03 13:48:10.000000000 +0100
@@ -1,112 +1,18 @@
-.\" Kudos to: xsltproc(1), help2man,
-.\" http://www.saxonica.com/documentation/using-xquery/commandline.html
-.TH SAXON9Q "1" "March 2006" "9.4" "User Commands"
+.TH SAXON9Q "1" "December 2012" "9.4" "User Commands"
 .SH NAME
-saxon9q \- manual page for saxon9q
+saxon9q \- Saxon XQuery processor
 .SH SYNOPSIS
 .B saxon9q
-[\fIoptions\fR]   \fIquery   \fR[ \fIparams\fR...]
+[\fIoptions\fR] \fI-q:queryfile \fR[\fIparam=value\fR...]
 .SH DESCRIPTION
-saxon9q runs a query contained in a file.
-
+saxon9q runs an XQuery query contained in a file.
 .SH OPTIONS
-The options must come first, then the file name containing the query, then the 
params.
+See:
 .TP
-The options are as follows (in any order):
+\fIhttp://www.saxonica.com/documentation/using-xquery/commandline.xml\fR
 .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.
+for command line usage.
+.SH "SEE ALSO"
+.BR saxon9 (1) .
 .SH AUTHOR
 Michael H. Kay <[email protected]>

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to