added a new entity and did some WS

# more documentation coming soon


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@159053 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Mehdi Achour 2004-05-19 18:46:47 +00:00
parent d467fb3053
commit a285c00fcd
5 changed files with 30 additions and 41 deletions

View file

@ -131,6 +131,11 @@ a file successfully opened by <function>fopen</function> or
<parameter>status</parameter> is the status parameter supplied to a successfull
call to <function>pcntl_waitpid</function>.</para>'>
<!-- XSLT Notes -->
<!ENTITY note.xslt.windows '<note><para>Please note that <emphasis>file://</emphasis>
is needed in front of path if you use Windows.</para></note>'>
<!-- Various notes -->
<!ENTITY note.randomseed '<note><simpara>As of PHP 4.2.0, there is no need
to seed the random number generator with <function>srand</function> or

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.11 $ -->
<!-- $Revision: 1.12 $ -->
<!-- splitted from ./en/functions/xslt.xml, last change in rev 1.3 -->
<refentry id="function.xslt-process">
<refnamediv>
@ -174,15 +174,7 @@ xslt_free($xh);
interpreted as strings by the Sablotron processor. In other words - you
cannot pass node-sets as parameters to the XSLT document.
</para>
<note>
<simpara>
Please note that <emphasis>file://</emphasis> is needed in front of path if you use Windows.
</simpara>
</note>
&note.xslt.windows;
</refsect1>
</refentry>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.4 $ -->
<!-- $Revision: 1.5 $ -->
<!-- splitted from ./en/functions/xslt.xml, last change in rev 1.3 -->
<refentry id="function.xslt-set-base">
<refnamediv>
@ -23,11 +23,7 @@
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 <constant>__FILE__</constant> constant. Prior to 4.3, the default base URI was less predictable.
</para>
<note>
<simpara>
Please note that <emphasis>file://</emphasis> is needed in front of path if you use Windows.
</simpara>
</note>
&note.xslt.windows;
</refsect1>
</refentry>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.2 $ -->
<!-- $Revision: 1.3 $ -->
<!-- splitted from ./en/functions/xslt.xml, last change in rev 1.3 -->
<refentry id="function.xslt-set-encoding">
<refnamediv>
@ -15,8 +15,9 @@
</methodsynopsis>
<para>
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.
<productname>Sablotron</productname> backend, this option is only
available when you compile <productname>Sablotron</productname> with
encoding support.
</para>
</refsect1>
</refentry>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.5 $ -->
<!-- $Revision: 1.6 $ -->
<!-- splitted from ./en/functions/xslt.xml, last change in rev 1.3 -->
<refentry id="function.xslt-set-log">
<refnamediv>
@ -18,36 +18,35 @@
<varlistentry>
<term><parameter>xh</parameter></term>
<listitem>
<simpara>
A reference to the XSLT parser.
</simpara>
<simpara>
A reference to the XSLT parser.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>log</parameter></term>
<listitem>
<simpara>
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 parameter is either a boolean value which toggles logging on and
off, or a string containing the logfile in which log errors too.
</simpara>
</listitem>
</varlistentry>
</variablelist></para>
<para>
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.
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.
</para>
<para>
By default logging is disabled, in order to enable logging you must first call
<function>xslt_set_log</function> 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:
By default logging is disabled, in order to enable logging you must
first call <function>xslt_set_log</function> 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:
<example>
<title>
Using the XSLT Logging features
</title>
<title>Using the XSLT Logging features</title>
<programlisting role="php">
<![CDATA[
<?php
@ -65,11 +64,7 @@ xslt_free($xh);
</programlisting>
</example>
</para>
<note>
<simpara>
Please note that <emphasis>file://</emphasis> is needed in front of path if you use Windows.
</simpara>
</note>
&note.xslt.windows;
</refsect1>
</refentry>