diff --git a/reference/xslt/functions/xslt-backend-info.xml b/reference/xslt/functions/xslt-backend-info.xml index 835ac3d2ac..7408b4a1b1 100755 --- a/reference/xslt/functions/xslt-backend-info.xml +++ b/reference/xslt/functions/xslt-backend-info.xml @@ -1,32 +1,30 @@ - - - - xslt_backend_info - - Returns the information on the compilation settings of the backend - - - - Description - - stringxslt_backend_info - - - - xslt_backend_info returns a string with - information about the compilation setting of the backend - or an error string when no information available. - - - - &reftitle.seealso; - - xslt_backend_name&listendand; - xslt_backend_version. - - - + + + + xslt_backend_info + Returns the information on the compilation settings of the backend + + + Description + + stringxslt_backend_info + + + + xslt_backend_info returns a string with + information about the compilation setting of the backend + or an error string when no information available. + + + + &reftitle.seealso; + + xslt_backend_name&listendand; + xslt_backend_version. + + + - - - xslt_backend_name - - Returns the name of the backend - - - - Description - - stringxslt_backend_name - - - - xslt_backend_name will always return - Sablotron. - - - - &reftitle.examples; - - <function>xslt_backend_name</function> example - + + + + xslt_backend_name + Returns the name of the backend + + + Description + + stringxslt_backend_name + + + + xslt_backend_name will always return + Sablotron. + + + + &reftitle.examples; + + <function>xslt_backend_name</function> example + ]]> - - - - - &reftitle.seealso; - - xslt_backend_info&listendand; - xslt_backend_version. - - - + + + + + &reftitle.seealso; + + xslt_backend_info&listendand; + xslt_backend_version. + + + - - - xslt_backend_version - - Returns the version number of Sablotron - - - - Description - - stringxslt_backend_version - - - - xslt_backend_version returns the version - number of Sablotron if available, - &false; otherwise. - - - - &reftitle.examples; - - <function>xslt_backend_version</function> example - + + + + xslt_backend_version + Returns the version number of Sablotron + + + Description + + stringxslt_backend_version + + + + xslt_backend_version returns the version + number of Sablotron if available, + &false; otherwise. + + + + &reftitle.examples; + + <function>xslt_backend_version</function> example + ]]> - - - - - &reftitle.seealso; - - xslt_backend_name&listendand; - xslt_backend_info. - - - + + + + + &reftitle.seealso; + + xslt_backend_name&listendand; + xslt_backend_info. + + + + - - - xslt_create - Create a new XSLT processor - - - Description - - resourcexslt_create - - - - Create and return a new XSLT processor resource for manipulation by the - other XSLT functions. - - - - &reftitle.examples; - - <function>xslt_create</function> example - + + + xslt_create + Create a new XSLT processor + + + Description + + resourcexslt_create + + + + Create and return a new XSLT processor resource for manipulation by the + other XSLT functions. + + + + &reftitle.examples; + + <function>xslt_create</function> example + your XML */ - /* $xsl -> XSLT file */ + /* $xsl -> XSLT file */ $path = 'include'; $arguments = array('/_xml' => $xmldata); @@ -41,19 +41,19 @@ function xml2html($xmldata, $xsl) } xslt_free($xsltproc); return $html; -} +} ?> ]]> - - - - - &reftitle.seealso; - - xslt_free. - - - + + + + + &reftitle.seealso; + + xslt_free. + + + + - - - xslt_errno - Returns an error number - - - Description - - intxslt_errno - resourcexh - - - Returns an error code describing the last error that occurred on the - passed XSLT processor. - - - - &reftitle.seealso; - - xslt_error. - - - + + + xslt_errno + Returns an error number + + + Description + + intxslt_errno + resourcexh + + + Returns an error code describing the last error that occurred on the + passed XSLT processor. + + + + &reftitle.seealso; + + xslt_error. + + + + - - - xslt_error - Returns an error string - - - Description - - stringxslt_error - resourcexh - - - Returns a string describing the last error that occurred on the - passed XSLT processor. - - - - &reftitle.examples; - - - Handling errors using the <function>xslt_error</function> and - <function>xslt_errno</function> functions. - - + + + xslt_error + Returns an error string + + + Description + + stringxslt_error + resourcexh + + + Returns a string describing the last error that occurred on the + passed XSLT processor. + + + + &reftitle.examples; + + + Handling errors using the <function>xslt_error</function> and + <function>xslt_errno</function> functions. + + ]]> - - - - - &reftitle.seealso; - - xslt_errno. - - - + + + + + &reftitle.seealso; + + xslt_errno. + + + + - - - xslt_free - Free XSLT processor - - - Description - - voidxslt_free - resourcexh - - - Free the XSLT processor identified by the given handle. - - - - &reftitle.seealso; - - xslt_create - - - + + + xslt_free + Free XSLT processor + + + Description + + voidxslt_free + resourcexh + + + Free the XSLT processor identified by the given handle. + + + + &reftitle.seealso; + + xslt_create + + + - - - xslt_getopt - - Get options on a given xsl processor - - - - Description - - intxslt_getopt - resourceprocessor - - - xslt_getopt returns the options on the given - processor. - - - - &reftitle.seealso; - - xslt_setopt. - - - + + + + xslt_getopt + Get options on a given xsl processor + + + Description + + intxslt_getopt + resourceprocessor + + + xslt_getopt returns the options on the given + processor. + + + + &reftitle.seealso; + + xslt_setopt. + + + + - - - xslt_process - Perform an XSLT transformation - - - Description - - mixedxslt_process - resourcexh - stringxmlcontainer - stringxslcontainer - stringresultcontainer - arrayarguments - arrayparameters - - - The xslt_process function is the crux of the new - XSLT extension. It allows you to perform an XSLT transformation using - almost any type of input source - the containers. This is accomplished - through the use of argument buffers -- a concept taken from the Sablotron - XSLT processor (currently the only XSLT processor this extension supports). - The input containers default to a filename 'containing' the document to be - processed. The result container defaults to a filename for the transformed - document. If the result container is not specified - i.e. - &null; - than the result is returned. - - - - - As of PHP 4.0.6, this function no longer takes XML strings in - xmlcontainer or - xslcontainer. Passing a string containing XML - to either of these parameters will result in a segmentation fault in - Sablotron versions up to and including version 0.95. - - - - - Containers can also be set via the arguments - array (see below). - - - The simplest type of transformation with the - xslt_process function is the transformation of an - XML file with an XSLT file, placing the result in a third file containing - the new XML (or HTML) document. Doing this with sablotron is really - quite easy... - - - Using the <function>xslt_process</function> to transform an XML - file and a XSL file to a new XML file - + + + xslt_process + Perform an XSLT transformation + + + Description + + mixedxslt_process + resourcexh + stringxmlcontainer + stringxslcontainer + stringresultcontainer + arrayarguments + arrayparameters + + + The xslt_process function is the crux of the new + XSLT extension. It allows you to perform an XSLT transformation using + almost any type of input source - the containers. This is accomplished + through the use of argument buffers -- a concept taken from the Sablotron + XSLT processor (currently the only XSLT processor this extension supports). + The input containers default to a filename 'containing' the document to be + processed. The result container defaults to a filename for the transformed + document. If the result container is not specified - i.e. + &null; - than the result is returned. + + + + + As of PHP 4.0.6, this function no longer takes XML strings in + xmlcontainer or + xslcontainer. Passing a string containing XML + to either of these parameters will result in a segmentation fault in + Sablotron versions up to and including version 0.95. + + + + + Containers can also be set via the arguments + array (see below). + + + The simplest type of transformation with the + xslt_process function is the transformation of an + XML file with an XSLT file, placing the result in a third file containing + the new XML (or HTML) document. Doing this with sablotron is really + quite easy... + + + Using the <function>xslt_process</function> to transform an XML + file and a XSL file to a new XML file + ]]> - - - - While this functionality is great, many times, especially in a web environment, you want to - be able to print out your results directly. Therefore, if you omit the third argument to - the xslt_process function (or provide a NULL value for the argument), it - will automatically return the value of the XSLT transformation, instead of writing it to a - file... - - - - Using the <function>xslt_process</function> to transform an XML file and a XSL file - to a variable containing the resulting XML data - + + + + While this functionality is great, many times, especially in a web environment, you want to + be able to print out your results directly. Therefore, if you omit the third argument to + the xslt_process function (or provide a NULL value for the argument), it + will automatically return the value of the XSLT transformation, instead of writing it to a + file... + + + + Using the <function>xslt_process</function> to transform an XML file and a XSL file + to a variable containing the resulting XML data + \n"; } else { echo "Sorry, sample.xml could not be transformed by sample.xsl into"; - echo " the \$result variable the reason is that " . xslt_error($xh); + echo " the \$result variable the reason is that " . xslt_error($xh); echo " and the error code is " . xslt_errno($xh); } @@ -115,26 +115,26 @@ xslt_free($xh); ?> ]]> - - - - - The above two cases are the two simplest cases there are when it comes to XSLT transformation - and I'd dare say that they are the most common cases, however, sometimes you get your XML and - XSLT code from external sources, such as a database or a socket. In these cases you'll have - the XML and/or XSLT data in a variable -- and in production applications the overhead of dumping - these to file may be too much. This is where XSLT's "argument" syntax, comes to the - rescue. Instead of files as the XML and XSLT arguments to the xslt_process - function, you can specify "argument place holders" which are then substituted by values - given in the arguments array (5th parameter to the xslt_process function). - The following is an example of processing XML and XSLT into a result variable without the use - of files at all. - - - - Using the <function>xslt_process</function> to transform a variable containing XML data - and a variable containing XSL data into a variable containing the resulting XML data - + + + + + The above two cases are the two simplest cases there are when it comes to XSLT transformation + and I'd dare say that they are the most common cases, however, sometimes you get your XML and + XSLT code from external sources, such as a database or a socket. In these cases you'll have + the XML and/or XSLT data in a variable -- and in production applications the overhead of dumping + these to file may be too much. This is where XSLT's "argument" syntax, comes to the + rescue. Instead of files as the XML and XSLT arguments to the xslt_process + function, you can specify "argument place holders" which are then substituted by values + given in the arguments array (5th parameter to the xslt_process function). + The following is an example of processing XML and XSLT into a result variable without the use + of files at all. + + + + Using the <function>xslt_process</function> to transform a variable containing XML data + and a variable containing XSL data into a variable containing the resulting XML data + \n"; @@ -163,22 +163,22 @@ if ($result) { xslt_free($xh); ?> ]]> - - - - - Finally, the last argument to the xslt_process - function represents an array for any top-level parameters that you want to - pass to the XSLT document. These parameters can then be accessed within - your XSL files using the <xsl:param name="parameter_name"> - instruction. The parameters must be UTF-8 encoded and their values will be - interpreted as strings by the Sablotron processor. - In other words - you cannot pass node-sets as parameters to the XSLT document. - - - - Passing PHP variables to XSL files - + + + + + Finally, the last argument to the xslt_process + function represents an array for any top-level parameters that you want to + pass to the XSLT document. These parameters can then be accessed within + your XSL files using the <xsl:param name="parameter_name"> + instruction. The parameters must be UTF-8 encoded and their values will be + interpreted as strings by the Sablotron processor. + In other words - you cannot pass node-sets as parameters to the XSLT document. + + + + Passing PHP variables to XSL files + // XSL string $xsl = ' - @@ -219,19 +219,19 @@ echo xslt_process($xh, 'arg:/_xml', 'arg:/_xsl', NULL, $arguments, $parameters); ?> ]]> - - &example.outputs; - + + &example.outputs; + My node set : <foo>bar</foo> ]]> - - - - ¬e.xslt.windows; - - + + + + ¬e.xslt.windows; + + + - - - xslt_set_base - Set the base URI for all XSLT transformations - - - Description - - voidxslt_set_base - resourcexh - stringuri - - - Sets the base URI for all XSLT transformations, the base URI is used - with Xpath instructions to resolve document() and other commands which - access external resources. It is also used to resolve URIs for the <xsl:include> - and <xsl:import> elements. - - - As of 4.3, the default base URI is the directory of the executing script. In effect, it is the - directory name value of the __FILE__ constant. Prior to 4.3, the default base URI was less predictable. - - ¬e.xslt.windows; - - + + + xslt_set_base + Set the base URI for all XSLT transformations + + + Description + + voidxslt_set_base + resourcexh + stringuri + + + Sets the base URI for all XSLT transformations, the base URI is used + with Xpath instructions to resolve document() and other commands which + access external resources. It is also used to resolve URIs for the <xsl:include> + and <xsl:import> elements. + + + As of 4.3, the default base URI is the directory of the executing script. + In effect, it is the directory name value of the __FILE__ + constant. Prior to 4.3, the default base URI was less predictable. + + ¬e.xslt.windows; + + + - - - xslt_set_encoding - Set the encoding for the parsing of XML documents - - - Description - - voidxslt_set_encoding - resourcexh - stringencoding - - - Set the output encoding for the XSLT transformations. When using the - Sablotron backend, this option is only - available when you compile Sablotron with - encoding support. - - - + + + xslt_set_encoding + Set the encoding for the parsing of XML documents + + + Description + + voidxslt_set_encoding + resourcexh + stringencoding + + + Set the output encoding for the XSLT transformations. When using the + Sablotron backend, this option is only + available when you compile Sablotron with + encoding support. + + + + - - - xslt_set_error_handler - Set an error handler for a XSLT processor - - - Description - - voidxslt_set_error_handler - resourcexh - mixedhandler - - - Set an error handler function for the XSLT processor given by - xh, this function will be called whenever an - error occurs in the XSLT transformation (this function is also called - for notices). - - - The user function needs to accept four parameters: the XSLT processor, - the error level, the error code and an array of messages. The function - can be shown as: - - error_handler - resourcexh - interror_level - interror_code - arraymessages - - - - - &reftitle.examples; - - <function>xslt_set_error_handler</function> Example - + + + xslt_set_error_handler + Set an error handler for a XSLT processor + + + Description + + voidxslt_set_error_handler + resourcexh + mixedhandler + + + Set an error handler function for the XSLT processor given by + xh, this function will be called whenever an + error occurs in the XSLT transformation (this function is also called + for notices). + + + The user function needs to accept four parameters: the XSLT processor, + the error level, the error code and an array of messages. The function + can be shown as: + + error_handler + resourcexh + interror_level + interror_code + arraymessages + + + + + &reftitle.examples; + + <function>xslt_set_error_handler</function> Example + ]]> - - &example.outputs.similar; - + + &example.outputs.similar; + @@ -98,17 +98,17 @@ array(4) { } } ]]> - - - - - &reftitle.seealso; - - xslt_set_object if you want to use an - object method as handler. - - - + + + + + &reftitle.seealso; + + xslt_set_object if you want to use an + object method as handler. + + + + - - - xslt_set_log - Set the log file to write log messages to - - - Description - - voidxslt_set_log - resourcexh - mixedlog - - - - - xh - - - A reference to the XSLT parser. - - - - - log - - - This parameter is either a boolean value which toggles logging on and - off, or a string containing the logfile in which log errors too. - - - - - - This function allows you to set the file in which you want XSLT log - messages to, XSLT log messages are different than error messages, in - that log messages are not actually error messages but rather messages - related to the state of the XSLT processor. They are useful for - debugging XSLT, when something goes wrong. - - - By default logging is disabled, in order to enable logging you must - first call xslt_set_log with a boolean parameter - which enables logging, then if you want to set the log file to debug to, - you must then pass it a string containing the filename. - - ¬e.xslt.windows; - - - &reftitle.examples; - - Using the XSLT Logging features - + + + xslt_set_log + Set the log file to write log messages to + + + Description + + voidxslt_set_log + resourcexh + mixedlog + + + + + xh + + + A reference to the XSLT parser. + + + + + log + + + This parameter is either a boolean value which toggles logging on and + off, or a string containing the logfile in which log errors too. + + + + + + This function allows you to set the file in which you want XSLT log + messages to, XSLT log messages are different than error messages, in + that log messages are not actually error messages but rather messages + related to the state of the XSLT processor. They are useful for + debugging XSLT, when something goes wrong. + + + By default logging is disabled, in order to enable logging you must + first call xslt_set_log with a boolean parameter + which enables logging, then if you want to set the log file to debug to, + you must then pass it a string containing the filename. + + ¬e.xslt.windows; + + + &reftitle.examples; + + Using the XSLT Logging features + ]]> - - - - + + + + - - - xslt_set_object - - Sets the object in which to resolve callback functions - - - - Description - - boolxslt_set_object - resourceprocessor - objectobj - - - This function allows to use the processor inside - an object and to resolve all callback functions - in it. - - - The callback functions can be declared with - xml_set_sax_handlers, - xslt_set_scheme_handlers or - xslt_set_error_handler and are assumed to be methods - of object. - - - - &reftitle.examples; - - Using your own error handler as a method - + + + + xslt_set_object + Sets the object in which to resolve callback functions + + + Description + + boolxslt_set_object + resourceprocessor + objectobj + + + This function allows to use the processor inside + an object and to resolve all callback functions + in it. + + + The callback functions can be declared with + xml_set_sax_handlers, + xslt_set_scheme_handlers or + xslt_set_error_handler and are assumed to be methods + of object. + + + + &reftitle.examples; + + Using your own error handler as a method + _xh = xslt_create(); @@ -59,10 +57,10 @@ class my_xslt_processor { ?> ]]> - - - - + + + + + - - - xslt_set_sax_handler - Set SAX handlers for a XSLT processor - - - Description - - voidxslt_set_sax_handler - resourcexh - arrayhandlers - - - Set SAX handlers on the resource handle given by - xh. SAX handlers should be a two dimensional array - with the format (all top level elements are optional): - - + + + xslt_set_sax_handler + Set SAX handlers for a XSLT processor + + + Description + + voidxslt_set_sax_handler + resourcexh + arrayhandlers + + + Set SAX handlers on the resource handle given by + xh. SAX handlers should be a two dimensional array + with the format (all top level elements are optional): + + +[document] => array( start document handler, end document handler ), -[element] => +[element] => array( start element handler, end element handler ), -[namespace] => +[namespace] => array( start namespace handler, end namespace handler @@ -41,11 +41,11 @@ array( [character] => character data handler ) ]]> - - - - - + + + + + + - - - xslt_set_sax_handlers - - Set the SAX handlers to be called when the XML document gets processed - - - - Description - - voidxslt_set_sax_handlers - resourceprocessor - arrayhandlers - - - xslt_set_sax_handlers registers the SAX - handlers for the document, given a XSLT - processor resource. - - - handlers should be an array in the following format: - - + + + xslt_set_sax_handlers + Set the SAX handlers to be called when the XML document gets processed + + + Description + + voidxslt_set_sax_handlers + resourceprocessor + arrayhandlers + + + xslt_set_sax_handlers registers the SAX + handlers for the document, given a XSLT + processor resource. + + + handlers should be an array in the following format: + + ]]> - - - Where the functions follow the syntax described for the scheme handler - functions. - - - - The given array does not need to contain all of the different sax - handler elements (although it can), but it only needs to conform to - "handler" => "function" format described above. - - - - Each of the individual SAX handler functions are in the format below: - - - - - start_doc - resourceprocessor - - - - - - - end_doc - resourceprocessor - - - - - - - start_element - resourceprocessor - stringname - arrayattributes - - - - - - - end_element - resourceprocessor - stringname - - - - - - - start_namespace - resourceprocessor - stringprefix - stringuri - - - - - - - end_namespace - resourceprocessor - stringprefix - - - - - - - comment - resourceprocessor - stringcontents - - - - - - - pi - resourceprocessor - stringtarget - stringcontents - - - - - - - characters - resourceprocessor - stringcontents - - - - - - - Using xslt_set_sax_handlers doesn't look very different than - running a SAX parser like xml_parse on the result of an - xslt_process transformation. - - - - &reftitle.examples; - - <function>xslt_set_sax_handlers</function> Example - + + + Where the functions follow the syntax described for the scheme handler + functions. + + + + The given array does not need to contain all of the different sax + handler elements (although it can), but it only needs to conform to + "handler" => "function" format described above. + + + + Each of the individual SAX handler functions are in the format below: + + + + + start_doc + resourceprocessor + + + + + + + end_doc + resourceprocessor + + + + + + + start_element + resourceprocessor + stringname + arrayattributes + + + + + + + end_element + resourceprocessor + stringname + + + + + + + start_namespace + resourceprocessor + stringprefix + stringuri + + + + + + + end_namespace + resourceprocessor + stringprefix + + + + + + + comment + resourceprocessor + stringcontents + + + + + + + pi + resourceprocessor + stringtarget + stringcontents + + + + + + + characters + resourceprocessor + stringcontents + + + + + + + Using xslt_set_sax_handlers doesn't look very different than + running a SAX parser like xml_parse on the result of an + xslt_process transformation. + + + + &reftitle.examples; + + <function>xslt_set_sax_handlers</function> Example + tag and then displays the +// Here's a simple example that applies strtoupper() on +// the content of every tag and then displays the // resulting XML tree: $xml=' @@ -192,30 +190,30 @@ $xsl=' '; // Handlers : -function start_document() +function start_document() { // start reading the document } -function end_document() +function end_document() { // end reading the document } -function start_element($parser, $name, $attributes) +function start_element($parser, $name, $attributes) { global $result,$tag; $result .= "<". $name . ">"; $tag = $name; } -function end_element($parser, $name) +function end_element($parser, $name) { global $result; $result .= ""; } -function characters($parser, $data) +function characters($parser, $data) { global $result,$tag; if ($tag == "auteur" ) { @@ -235,15 +233,15 @@ xslt_process($xh, 'arg:/_xml', 'arg:/_xsl', NULL, array("/_xml"=>$xml, "/_xsl"=> xslt_free($xh); ?> ]]> - - - - You can also use xslt_set_object if you want to - implement your handlers in an object. - - - Object oriented handler - + + + + You can also use xslt_set_object if you want to + implement your handlers in an object. + + + Object oriented handler + _xh, $handlers); - + xslt_process($this->_xh, 'arg:/_xml', 'arg:/_xsl', NULL, array("/_xml"=>$xml, "/_xsl"=>$xsl)); xslt_free($this->_xh); } - function start_document() + function start_document() { // start reading the document } @@ -303,7 +301,7 @@ class data_sax_handler { } $this->buffer .= $data; } - + function get_buffer() { return $this->buffer; } @@ -314,11 +312,11 @@ $exec = new data_sax_handler($xml, $xsl); ?> ]]> - - - Both examples will output: - - + + + Both examples will output: + + GUSTAVE FLAUBERT @@ -327,10 +325,10 @@ $exec = new data_sax_handler($xml, $xsl); VIRGINIA WOOLF ]]> - - - - + + + + + - - - xslt_set_scheme_handler - Set Scheme handlers for a XSLT processor - - - Description - - voidxslt_set_scheme_handler - resourcexh - arrayhandlers - - - Set Scheme handlers on the resource handle given by - xh. Scheme handlers should be an array with the - format (all elements are optional): - - + + + xslt_set_scheme_handler + Set Scheme handlers for a XSLT processor + + + Description + + voidxslt_set_scheme_handler + resourcexh + arrayhandlers + + + Set Scheme handlers on the resource handle given by + xh. Scheme handlers should be an array with the + format (all elements are optional): + + get all handler, @@ -28,11 +28,11 @@ array( [close] => close handler ) ]]> - - - - - + + + + + + - - - xslt_set_scheme_handlers - - Set the scheme handlers for the XSLT processor - - - - Description - - voidxslt_set_scheme_handlers - resourceprocessor - arrayhandlers - - - &warn.undocumented.func; - - - + + + xslt_set_scheme_handlers + Set the scheme handlers for the XSLT processor + + + Description + + voidxslt_set_scheme_handlers + resourceprocessor + arrayhandlers + + + &warn.undocumented.func; + + + - - - xslt_setopt - - Set options on a given xsl processor - - - - Description - - mixedxslt_setopt - resourceprocessor - intnewmask - - - xslt_setopt sets the options specified by - newmask on the given processor. - Returns the number of previous mask is possible, &true; otherwise, - &false; in case of an error. - - - newmask is a bitmask constructed with the following - constants: - - - - XSLT_SABOPT_PARSE_PUBLIC_ENTITIES - Tell the processor - to parse public entities. By default this has been turned off. - - - - - XSLT_SABOPT_DISABLE_ADDING_META - Do not add the meta - tag "Content-Type" for HTML output. The default is set during the compilation - of the processor. - - - - - XSLT_SABOPT_DISABLE_STRIPPING - Suppress the whitespace - stripping (on data files only). - - - - - XSLT_SABOPT_IGNORE_DOC_NOT_FOUND - Consider unresolved - documents (the document() function) non-lethal. - - - - - - - &reftitle.examples; - - <function>xslt_setopt</function> Example - + + + + xslt_setopt + Set options on a given xsl processor + + + Description + + mixedxslt_setopt + resourceprocessor + intnewmask + + + xslt_setopt sets the options specified by + newmask on the given processor. + Returns the number of previous mask is possible, &true; otherwise, + &false; in case of an error. + + + newmask is a bitmask constructed with the following + constants: + + + + XSLT_SABOPT_PARSE_PUBLIC_ENTITIES - Tell the processor + to parse public entities. By default this has been turned off. + + + + + XSLT_SABOPT_DISABLE_ADDING_META - Do not add the meta + tag "Content-Type" for HTML output. The default is set during the compilation + of the processor. + + + + + XSLT_SABOPT_DISABLE_STRIPPING - Suppress the whitespace + stripping (on data files only). + + + + + XSLT_SABOPT_IGNORE_DOC_NOT_FOUND - Consider unresolved + documents (the document() function) non-lethal. + + + + + + + &reftitle.examples; + + <function>xslt_setopt</function> Example + ]]> - - - - - &reftitle.seealso; - - xslt_getopt. - - - + + + + + &reftitle.seealso; + + xslt_getopt. + + +