subbie Sun Jul 20 10:25:45 2003 EDT
Modified files:
/phpdoc-el/reference/mail ini.xml reference.xml
/phpdoc/en/reference/mail/functions ezmlm-hash.xml mail.xml
Log:
corrected errror in translation move
Index: phpdoc-el/reference/mail/ini.xml
diff -u phpdoc-el/reference/mail/ini.xml:1.1 phpdoc-el/reference/mail/ini.xml:1.2
--- phpdoc-el/reference/mail/ini.xml:1.1 Sun Jul 20 06:46:04 2003
+++ phpdoc-el/reference/mail/ini.xml Sun Jul 20 10:25:45 2003
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="iso-8859-7"?>
-<!-- $Revision: 1.1 $ -->
-<!-- En-Revision: 1.3 Maintainer: legionnaire Status: ready -->
+<!-- $Revision: 1.2 $ -->
+<!-- EN-Revision: 1.3 Maintainer: legionnaire Status: ready -->
<section id="mail.configuration">
&reftitle.runtime;
&extension.runtime;
Index: phpdoc-el/reference/mail/reference.xml
diff -u phpdoc-el/reference/mail/reference.xml:1.1
phpdoc-el/reference/mail/reference.xml:1.2
--- phpdoc-el/reference/mail/reference.xml:1.1 Sun Jul 20 06:46:04 2003
+++ phpdoc-el/reference/mail/reference.xml Sun Jul 20 10:25:45 2003
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-7"?>
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
<!-- En-Revision: 1.8 Maintainer: legionnaire Status: ready -->
<reference id="ref.mail">
<title>����������� ��� Mail</title>
Index: phpdoc/en/reference/mail/functions/ezmlm-hash.xml
diff -u phpdoc/en/reference/mail/functions/ezmlm-hash.xml:1.11
phpdoc/en/reference/mail/functions/ezmlm-hash.xml:1.12
--- phpdoc/en/reference/mail/functions/ezmlm-hash.xml:1.11 Sun Jul 20 04:02:20
2003
+++ phpdoc/en/reference/mail/functions/ezmlm-hash.xml Sun Jul 20 10:25:45 2003
@@ -1,24 +1,25 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.11 $ -->
+<?xml version="1.0" encoding="iso-8859-7"?>
+<!-- $Revision: 1.12 $ -->
+<!-- En-Revision: 1.9 Maintainer: legionnaire Status: ready -->
<!-- splitted from ./en/functions/mail.xml, last change in rev 1.6 -->
<refentry id="function.ezmlm-hash">
<refnamediv>
<refname>ezmlm_hash</refname>
- <refpurpose>Calculate the hash value needed by EZMLM</refpurpose>
+ <refpurpose>���������� ��� ���� hash ��� ���������� ��� �� EZMLM</refpurpose>
</refnamediv>
<refsect1>
- <title>Description</title>
+ <title>���������</title>
<methodsynopsis>
<type>int</type><methodname>ezmlm_hash</methodname>
<methodparam><type>string</type><parameter>addr</parameter></methodparam>
</methodsynopsis>
<simpara>
- <function>ezmlm_hash</function> calculates the hash value needed
- when keeping EZMLM mailing lists in a MySQL database.
+ � <function>ezmlm_hash</function> ���������� ��� ���� hash ��� ����������
+ ���� ��� ��������� EZMLM mailing lists �� ��� MySQL database.
</simpara>
<para>
<example>
- <title>Calculating the hash and subscribing a user</title>
+ <title>������������� �� hash ��� ����������� ��� ������</title>
<programlisting>
<![CDATA[
$user = "[EMAIL PROTECTED]";
Index: phpdoc/en/reference/mail/functions/mail.xml
diff -u phpdoc/en/reference/mail/functions/mail.xml:1.19
phpdoc/en/reference/mail/functions/mail.xml:1.20
--- phpdoc/en/reference/mail/functions/mail.xml:1.19 Sun Jul 20 04:02:20 2003
+++ phpdoc/en/reference/mail/functions/mail.xml Sun Jul 20 10:25:45 2003
@@ -1,13 +1,14 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.19 $ -->
+<?xml version="1.0" encoding="iso-8859-7"?>
+<!-- $Revision: 1.20 $ -->
+<!-- En-Revision: 1.17 Maintainer: legionnaire Status: ready -->
<!-- splitted from ./en/functions/mail.xml, last change in rev 1.2 -->
<refentry id="function.mail">
<refnamediv>
<refname>mail</refname>
- <refpurpose>send mail</refpurpose>
+ <refpurpose>�������� mail</refpurpose>
</refnamediv>
<refsect1>
- <title>Description</title>
+ <title>���������</title>
<methodsynopsis>
<type>bool</type><methodname>mail</methodname>
<methodparam><type>string</type><parameter>to</parameter></methodparam>
@@ -17,19 +18,19 @@
<methodparam
choice="opt"><type>string</type><parameter>additional_parameters</parameter></methodparam>
</methodsynopsis>
<simpara>
- <function>mail</function> automatically mails the message
- specified in <parameter>message</parameter> to the receiver
- specified in <parameter>to</parameter>. Multiple recipients can
- be specified by putting a comma between each address in
- <parameter>to</parameter>. Email with attachments and special
- types of content can be sent using this function. This is
- accomplished via MIME-encoding - for more information, see this
+ � <function>mail</function> �������� ������� �� mail �� ������
+ ���� �������� ��� <parameter>message</parameter> ���� ���������
+ ���� �������� ��� <parameter>to</parameter>. ��������� ���������� �������
+ �� �������� �� ��� �������� ���� �������� ������� �� ���� ��������� ���
+ <parameter>to</parameter>. Email �� ��������� ������ ��� ��������
+ ������ ������������ ������� �� ���������� �� ��� ����� ����� ��� ����������.
���� ����������������
+ ���� MIME-������������� - ��� ������������ �����������, ����� ����:
<ulink url="&url.email.mime.zend;">
- Zend article</ulink> or the <ulink url="&url.email.mime.pear;">
+ �� ����� Zend</ulink> � ���<ulink url="&url.email.mime.pear;">
PEAR Mime Classes</ulink>.
</simpara>
<simpara>
- The following RFC's may also be useful:
+ �� �������� RFC's ������� ������ �� ���������:
<ulink url="&url.rfc;1896">RFC 1896</ulink>,
<ulink url="&url.rfc;2045">RFC 2045</ulink>,
<ulink url="&url.rfc;2046">RFC 2046</ulink>,
@@ -38,29 +39,29 @@
<ulink url="&url.rfc;2049">RFC 2049</ulink>.
</simpara>
<para>
- <function>mail</function> returns &true; if the mail was successfully
- accepted for delivery, &false; otherwise.
+ � <function>mail</function> ���������� &true; ��� �� mail ����������
+ ��������, &false; �� �������� ���������.
</para>
<warning>
<para>
- The Windows implementation of <function>mail</function> differs in many
- ways from the Unix implementation. First, it doesn't use a local binary
- for composing messages but only operates on direct sockets which means a
- <literal>MTA</literal> is needed listening on a network socket (which
- can either on the localhost or a remote machine). Second, the custom
- headers like <literal>From:</literal>, <literal>Cc:</literal>,
- <literal>Bcc:</literal> and <literal>Date:</literal> are <emphasis
- role="strong">not</emphasis> interpreted by the <literal>MTA</literal>
- in the first place, but are parsed by <literal>PHP</literal>.
- <literal>PHP</literal> < 4.3 only supported the <literal>Cc:</literal>
- header element (and was case-sensitive). <literal>PHP</literal> >= 4.3
- supports all the mentioned header elements and is no longer
+ � ����������� ��� Windows ��� <function>mail</function> �������� �������������
+ ��� ��� ���������� ��� UNIX. ��������, ��� ������������ ��� ������ binary ������
+ ��� �� �������� �������� ���� ���� ������� �� direct sockets ��� �������� ���
���
+ <literal>MTA</literal> ���������� ��� �� "������" �� ��� network socket (��
�����
+ ������ �� ����� ���� ��� localhost -������- ���� ��� ������������� ��������).
������, �� custom
+ headers ���� <literal>From:</literal>, <literal>Cc:</literal>,
+ <literal>Bcc:</literal> ��� <literal>Date:</literal> <emphasis
+ role="strong">���</emphasis> ������������ ��� �� <literal>MTA</literal>
+ ���� ����, ���� ���������� ��� ��� <literal>PHP</literal>.
+ � <literal>PHP</literal> < 4.3 ���������� ���� �� �������� header
<literal>Cc:</literal>
+ (��� ���� case-sensitive). � <literal>PHP</literal> >= 4.3
+ ����������� ��� �� �������������� �������� header ��� ��� ����� �����
case-sensitive.
</para>
</warning>
<para>
<example>
- <title>Sending mail.</title>
+ <title>���������� mail.</title>
<programlisting>
<![CDATA[
<?php
@@ -71,21 +72,21 @@
</example>
</para>
<simpara>
- If a fourth string argument is passed, this string is inserted at
- the end of the header. This is typically used to add extra
- headers. Multiple extra headers are separated with a carriage return
- and newline.
+ ��� �������� ��� fourth string argument, ���� �� string ��������� ���
+ ����� ��� header. ���� ��������������� ������ ��� �� ���������� ��������
+ headers. ��������� �������� headers ���������� �� ��� return (enter)
+ ��� ��� ��� ������.
</simpara>
<note>
<para>
- You must use <literal>\r\n</literal> to separate headers, although
- some Unix mail transfer agents may work with just a single newline
+ ������ �� �������������� �� <literal>\r\n</literal> ��� �� �������� �� headers,
�� ���
+ ������� Unix mail transfer agents ��������� �� ��������� ���� �� ��� ��� ������
(<literal>\n</literal>).
</para>
</note>
<para>
<example>
- <title>Sending mail with extra headers.</title>
+ <title>���������� mail �� �������� headers.</title>
<programlisting>
<![CDATA[
<?php
@@ -99,17 +100,17 @@
</example>
</para>
<para>
- The <parameter>additional_parameters</parameter> parameter
- can be used to pass an additional parameter to the program configured
- to use when sending mail using the <literal>sendmail_path</literal>
- configuration setting. For example, this can be used to set the
- envelope sender address when using sendmail with the
- <literal>-f</literal> sendmail option. You may need to add
- the user that your web server runs as to your sendmail configuration
- to prevent a 'X-Warning' header from being added to the message when
- you set the envelope sender using this method.
+ � ���������� <parameter>additional_parameters</parameter>
+ ������ �� �������������� ��� �� �������� ��� ����������� ���������� ���
���������, �� ����� ���� ���������
+ �� ������������ ���� ��������� mail �� ����� ��� <literal>sendmail_path</literal>
+ ��������. ��� ����������, ���� ������ �� �������������� ��� �� ������
+ ��� ��������� ��� ��������� ���� ������� ����� ��� sendmail �� ��� �������
+ <literal>-f</literal>. ���� ��������� �� ����������
+ ��� ������, ��� � web server ��� ������������ ������� �� ��� ��������� ���
sendmail,
+ ��� �� ���������� �� ��������� ��� ������ ��� 'X-Warning' header ����
+ ������� ��� ��������� �� ���� �� ������.
<example>
- <title>Sending mail with extra headers and setting an additional command line
parameter.</title>
+ <title>���������� mail �� �������� headers ��� ��������� ��� �����������
command line ���������.</title>
<programlisting>
<![CDATA[
<?php
@@ -122,17 +123,17 @@
</para>
<note>
<para>
- This fifth parameter was added in PHP 4.0.5. Since PHP 4.2.3 this
- parameter is disabled in <link linkend="ini.safe-mode">safe_mode</link>
- and the <function>mail</function> function will expose a warning message
- and return &false; if you're trying to use it.
+ ���� � ������ ���������� ���������� ���� PHP 4.0.5. ��� ��� PHP 4.2.3 ����
+ � ���������� ����� ���������������� ��� <link
linkend="ini.safe-mode">safe_mode</link>
+ ��� � ��������� <function>mail</function> �� ��������� ��� ������ �������������
+ ��� �� ���������� &false; ��� ����������� �� ��� ���������������.
</para>
</note>
<para>
- You can also use simple string building techniques to build complex
- email messages.
+ �������� ������ �� ��������������� ����� �������� string building ��� ��
������������� ���������
+ �������� email.
<example>
- <title>Sending complex email.</title>
+ <title>���������� ��������� email.</title>
<programlisting>
<![CDATA[
<?php
@@ -185,21 +186,21 @@
</para>
<note>
<para>
- Make sure you do not have any newline characters in the
- <parameter>to</parameter> or <parameter>subject</parameter>,
- or the mail may not be sent properly.
+ ��������� �� ��� ����� ������ newline ���������� ���
+ <parameter>to</parameter> � <parameter>subject</parameter>,
+ ����������� �� mail ���� �� ��� ������ �����.
</para>
</note>
<note>
<para>
- The <parameter>to</parameter> parameter cannot be an address
- in the form of "Something <[EMAIL PROTECTED]>". The
- mail command will not parse this properly while talking with
- the MTA.
+ � <parameter>to</parameter> ���������� ��� ������ �� ����� ��� ���������
+ ��� ������ "Something <[EMAIL PROTECTED]>". �
+ ������ mail ��� �� �� �������� ����� ���� ��� ����������� �� ��
+ MTA.
</para>
</note>
<para>
- See also <function>imap_mail</function>.
+ ����� ������ <function>imap_mail</function>.
</para>
</refsect1>
</refentry>
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php