sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixed grammatical errors.

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@98112 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Erica Douglass 2002-10-04 08:20:20 +00:00
parent aac606cf7c
commit 762529d178
1 changed files with 33 additions and 33 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

66
reference/domxml/reference.xml
View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.7 $ -->
<!-- $Revision: 1.8 $ -->
<reference id="ref.domxml">
<title>DOM XML functions</title>
<titleabbrev>DOM XML</titleabbrev>
@ -9,32 +9,32 @@
&reftitle.intro;
&warn.experimental;
<para>
The domxml extension has been overhauled in PHP 4.3.0 to provide
a better compliance with the DOM standard. The extension still contains
many old functions, but they should not be used anymore. Especially those
non object oriented functions should be avoided.
The DOM XML extension has been overhauled in PHP 4.3.0 to better comply with
the DOM standard. The extension still contains
many old functions, but they should no longer be used. In particular, functions
that are not object-oriented should be avoided.
</para>
<para>
The extension allows you to operate on an XML document with the DOM API.
It also provides a function <function>domxml_xmltree</function> to turn the
complete XML document into a tree of PHP objects. Currently this
tree should be considered read-only - you can modify it but this
complete XML document into a tree of PHP objects. Currently, this
tree should be considered read-only &mdash; you can modify it, but this
would not make any sense since <function>DomDocument_dump_mem</function>
cannot be
applied to it. Therefore, if you want to read an XML file and write
a modified version use the <function>DomDocument_create_element</function>,
a modified version, use <function>DomDocument_create_element</function>,
<function>DomDocument_create_text_node</function>,
<function>set_attribute</function>, etc. and finally
<function>DomDocument_dump_mem</function> functions.
<function>set_attribute</function>, etc. and finally the
<function>DomDocument_dump_mem</function> function.
</para>
</section>
<section id="domxml.requirements">
&reftitle.required;
<para>
This extension make use of the
<ulink url="&url.domxml;">GNOME xml library</ulink>. Download
and install this library. You will need at least libxml-2.4.14
This extension makes use of the
<ulink url="&url.domxml;">GNOME XML library</ulink>. Download
and install this library. You will need at least libxml-2.4.14.
</para>
</section>
@ -50,10 +50,10 @@
<title>Deprecated functions</title>
<para>
There are quite a few functions that do not fit into the DOM standard and
should not be used anymore as listed in the following table.
should no longer be used. These functions are listed in the following table.
The function <function>DomNode_append_child</function> has changed its
behaviour. It now actually adds a child and not a sibling. If this
breaks your application use the non DOM function
behaviour. It now adds a child and not a sibling. If this
breaks your application, use the non-DOM function
<function>DomNode_append_sibling</function>.
</para>
<para>
@ -130,14 +130,14 @@
<row>
<entry>DomNode_new_child</entry>
<entry>Create a new node with e.g.
<function>DomDocument_create_element</function> und add it with
<function>DomDocument_create_element</function> and add it with
<function>DomNode_append_child</function>.
</entry>
</row>
<row>
<entry>DomNode_set_content</entry>
<entry>Create a new node with e.g.
<function>DomDocument_create_text_node</function> und add it with
<function>DomDocument_create_text_node</function> and add it with
<function>DomNode_append_child</function>.
</entry>
</row>
@ -164,27 +164,27 @@
<section id="domxml.classes">
<title>Classes</title>
<para>
The API of the module follows the DOM Level 2 standard as close
as possible. Consequently the API is fully object oriented.
The API of the module follows the DOM Level 2 standard as closely
as possible. Consequently, the API is fully object-oriented.
It is a good idea to have the DOM standard available when
using this module.
Though the API is object oriented there are many functions which can
be called in a non-object oriented way by passing the object to operate
on as the first argument. These function are mainly to retain compatibilty
to older versions of the extension but are not encouraged to use anymore
in new developments.
Though the API is object-oriented, there are many functions which can
be called in a non-object-oriented way by passing the object to operate
on as the first argument. These functions are mainly to retain compatibilty
to older versions of the extension, and should not be used when creating new
scripts.
</para>
<para>
This API differs from the official DOM API in two points. First, all
class attributes are implemented as functions with the same name and
secondly the function names follow the PHP naming convention. This means
This API differs from the official DOM API in two ways. First, all
class attributes are implemented as functions with the same name.
Secondly, the function names follow the PHP naming convention. This means
that a DOM function lastChild() will be written as last_child().
</para>
<para>
This module defines a number of classes, which are listed &mdash;
including their
method &mdash; in the following tables. Classes with an equivalent in the
DOM Standard are named DOMxxx.
DOM standard are named DOMxxx.
</para>
<para>
@ -693,7 +693,7 @@
<para>
The classes DomDtd is derived from DomNode. DomComment is derived from
DomCData
DomCData.
</para>
</section>
@ -701,9 +701,9 @@
&reftitle.examples;
<para>
Many examples in this reference require an XML string. Instead of
repeating this string in any example it will be put into a file
and be included by each example. This include file is shown in the
following example section. You could also create an XML document
repeating this string in every example, it will be put into a file
which will be included by each example. This include file is shown in the
following example section. Alternatively, you could create an XML document and
read it with <function>DomDocument_open_file</function>.
</para>
<para>