n0nick Wed May 1 12:24:28 2002 EDT
Modified files:
/phpdoc/he/appendices reserved.xml
Log:
this file's bigger than i originally thought.. translated ~1/4 so far :O
Index: phpdoc/he/appendices/reserved.xml
diff -u phpdoc/he/appendices/reserved.xml:1.1 phpdoc/he/appendices/reserved.xml:1.2
--- phpdoc/he/appendices/reserved.xml:1.1 Wed May 1 11:58:41 2002
+++ phpdoc/he/appendices/reserved.xml Wed May 1 12:24:28 2002
@@ -1,28 +1,25 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
<appendix id="reserved">
- <title>List of Reserved Words</title>
+ <title>����� ����� ������</title>
<para>
- The following is a listing of predefined identifiers in PHP. None
- of the identifiers listed here should be used as identifiers in a
- your scripts. These lists include keywords and predefined variable,
- constant, and class names. These lists are neither exhaustive or
- complete.
+ ���� ����� �� ����� �������-���� �-PHP. ��� ������ ��� ��� �������
+ ���� ������ �������� ���. ������ ��� ������ ����� ���� �������, ������
+ ����� ������ �������-����. ������� ���� ���� ����� �� �����.
</para>
<sect1 id="reserved.keywords">
- <title>List of Keywords</title>
+ <title>����� �����-����</title>
<simpara>
- These words have special meaning in PHP. Some of them represent things
- which look like functions, some look like constants, and so on--but
- they're not, really: they are language constructs. You cannot use any
- of the following words as constants, class names, or function names.
- Using them as variable names is generally OK, but could lead to confusion.
+ ������ ���� ������ ������ �-PHP. ���� ������� ����� ������ ���������,
+ ���� ����� ������� ����� -- �� �����, �� ��: �� ���� ���. �� ����
+ ������ ��� ������� ����� �������, ���� ����� �� ���� �������.
+ ������ ��� ����� ������ ��� ����, �� ���� ������ ������.
</simpara>
<table>
- <title>PHP Keywords</title>
+ <title>����� ���� �-PHP</title>
<tgroup cols="4">
<tbody>
<row>
@@ -206,56 +203,54 @@
</sect1>
<sect1 id="reserved.variables">
- <title>Predefined Variables</title>
+ <title>������ ������ ����</title>
<sect2 id="reserved.variables.server">
- <title>Server variables: <varname>$_SERVER</varname></title>
+ <title>����� ���: <varname>$_SERVER</varname></title>
<note>
<simpara>
- Introduced in 4.1.0. In earlier versions, use
+ ���� �-4.1.0. ������� ������, ����� �
<varname>$HTTP_SERVER_VARS</varname>.
</simpara>
</note>
<simpara>
- <varname>$_SERVER</varname> is an array containing information
- such as headers, paths, and script locations. The entries in this
- array are created by the webserver. There is no guarantee that
- every webserver will provide any of these; servers may omit some,
- or provide others not listed here. That said, a large number of
- these variables are accounted for in the <ulink
- url="&url.cgispec;">CGI 1.1 specification</ulink>, so you should
- be able to expect those.
+ <varname>$_SERVER</varname> ��� ���� ����� ���� ���
+ ������, ������ ������� �������.
+ ������ ����� �� ������ ��-��� ����. ��� ����� ��� ��� ���
+ ���� �� ������ ����; ����� ������ ������ ���, �� ���� �����
+ ��� ������ ���. �� ���, ���� �� �������� ���� ������� �
+ <ulink url="&url.cgispec;">���� CGI 1.1</ulink>, �� ������ �����
+ ���.
</simpara>
<simpara>
- This is a 'superglobal', or automatic global, variable. This
- simply means that it is available in all scopes throughout a
- script. You don't need to do a <command>global
- $_SERVER;</command> to access it within functions or methods, as
- you do with <varname>$HTTP_SERVER_VARS</varname>.
+ ��� ����� '����-�������', �� ������� �������. ����, ��� ����
+ ��� ���� ���� ���� �����. ��� ���� ����� <command>global
+ $_SERVER;</command> ��� ���� ���� ���� �������� �� �����,
+ ��� �-<varname>$HTTP_SERVER_VARS</varname>.
</simpara>
<simpara>
- <varname>$HTTP_SERVER_VARS</varname> contains the same
- information, but is not an autoglobal.
+ <varname>$HTTP_SERVER_VARS</varname> ���� �� ���� �����, ��
+ ���� ������� �������.
</simpara>
<simpara>
- If the <link
- linkend="ini.register-globals">register_globals</link> directive
- is set, then these variables will also be made available in the
- global scope of the script; i.e., separate from the
- <varname>$_SERVER</varname> and <varname>$HTTP_SERVER_VARS</varname>
- arrays. For related information, see the security chapter titled
- <link linkend="security.registerglobals">Using Register
- Globals</link>. These individual globals are not autoglobals.
+ �� ������ <link linkend="ini.register-globals">register_globals</link>
+ ������, ������ ��� ���� ������ �� ����� �������� �� ������;
+ ����, ����� �������� <varname>$_SERVER</varname> �-
+ <varname>$HTTP_SERVER_VARS</varname>. ����� �������, ���
+ ��� ������ ���� <link linkend="security.registerglobals">�����
+ �-Register Globals</link>. �������� ������ ��� ���� ��������
+ ���������.
</simpara>
<simpara>
- You may or may not find any of the following elements in
- $_SERVER. Note that few, if any, of these will be available (or
- indeed have any meaning) if running PHP on the command line.
+
+ ��� ���� ����� �� �� ����� �� ��� ��������� ����� �-$_SERVER.
+ ��� �� ��� ���, �� ����, �������� ���� ���� ������ (�����
+ ��� ������ �����) �� PHP �� ����� ������.
</simpara>
<para>
@@ -264,15 +259,13 @@
<term>'<varname>PHP_SELF</varname>'</term>
<listitem>
<simpara>
- The filename of the currently executing script, relative to
- the document root. For instance,
- <varname>$_SERVER['PHP_SELF']</varname> in a script at the
- address <filename>http://example.com/test.php/foo.bar</filename>
- would be <filename>/test.php/foo.bar</filename>.
+ �� ����� �� ������ ��� ����, ���� ����� �������. ������,
+ <varname>$_SERVER['PHP_SELF']</varname> ������ ������
+ <filename>http://example.com/test.php/foo.bar</filename>
+ ���� <filename>/test.php/foo.bar</filename>.
</simpara>
<simpara>
- If PHP is running as a command-line processor, this variable
- is not available.
+ �� PHP �� ����� ����� ������, ����� �� �� ���� ����.
</simpara>
</listitem>
</varlistentry>