joseph Thu Dec 26 20:40:20 2002 EDT
Modified files:
/phpdoc/en/appendices wrappers.xml about.xml
Log:
updated
Index: phpdoc/en/appendices/wrappers.xml
diff -u phpdoc/en/appendices/wrappers.xml:1.8 phpdoc/en/appendices/wrappers.xml:1.9
--- phpdoc/en/appendices/wrappers.xml:1.8 Thu Oct 31 20:32:37 2002
+++ phpdoc/en/appendices/wrappers.xml Thu Dec 26 20:40:20 2002
@@ -1,19 +1,19 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.8 $ -->
+<!-- EN-Revision: 1.8 Maintainer: joseph Status: ready -->
<appendix id="wrappers">
- <title>List of Supported Protocols/Wrappers</title>
+ <title>Zoznam Podporovan�ch Protokolov/Bal��kov</title>
<para>
- The following is a list of the various URL style protocols that
- PHP has built-in for use with the filesystem functions such as
- <function>fopen</function> and <function>copy</function>.
- In addition to these wrappers, as of PHP 4.3, you can write
- your own wrappers using PHP script and
+ N�sleduj�ce je zoznam r�znych �t�lov�ch protokolov URL, ktor�
+ m� PHP vstavan� pre pou�itie s filesystem funkciami ako s�
+ <function>fopen</function> a <function>copy</function>.
+ Okrem t�chto bal��kov (wrappers), ako aj t�ch v PHP 4.3, si
+ m��te nap�sa� svoje vlastn� bal��ky s pou�it�m PHP skriptu a
<function>stream_register_wrapper</function>.
</para>
<section id="wrappers.http">
- <title>HTTP and HTTPS</title>
- <simpara>PHP 3, PHP 4. <filename>https://</filename> since PHP 4.3</simpara>
+ <title>HTTP a HTTPS</title>
+ <simpara>PHP 3, PHP 4. <filename>https://</filename> od PHP 4.3</simpara>
<itemizedlist>
<listitem><simpara><filename>http://example.com</filename></simpara></listitem>
@@ -22,39 +22,38 @@
<listitem><simpara><filename>https://user:[EMAIL PROTECTED]</filename></simpara></listitem>
</itemizedlist>
- <simpara>Allows read-only access to files/resources via HTTP 1.0,
- using the HTTP GET method. A <literal>Host:</literal> header is sent with the
request
- to handle name-based virtual hosts. If you have configured
- a <link linkend="ini.user-agent">user_agent</link> string using
- your ini file or the stream context, it will also be included
- in the request.
- </simpara>
- <simpara>
- Redirects have been supported since PHP 4.0.5; if you are using
- an earlier version you will need to include trailing slashes in
- your URLs.
- </simpara>
- <simpara>
- The stream allows access to the <emphasis>body</emphasis> of
- the resource; the headers are stored in the
- <varname>$http_response_header</varname> variable.
- Since PHP 4.3, the headers are available using
+ <simpara>Umo��uje pr�stup iba na ��tanie k s�borom/zdrojom cez HTTP 1.0
+ pou�it�m met�dy HTTP GET. Hlavi�ka <literal>Host:</literal> sa po�le
+ s po�iadavkou na zaistenie na mene zalo�en�ch virtu�lnych hostov. Ak
+ ste nakonfigurovali re�azec <link linkend="ini.user-agent">user_agent</link>
+ pou�it�m v�ho ini s�boru alebo pr�dov�ho kontextu, taktie� sa zahrnie
+ do po�iadavky.
+ </simpara>
+ <simpara>
+ Uz PHP 4.0.5 podporuje presmerovania; ak pou��vate predch�dzaj�ce
+ verzie, budete musie� zahrn�� vle�n� lom�tka do svojich URL adries.
+ </simpara>
+ <simpara>
+ Pr�d umo��uje pr�stup k <emphasis>telu</emphasis>
+ zdroja; hlavi�ky s� ulo�en� v premennej
+ <varname>$http_response_header</varname>.
+ Od PHP 4.3, hlavi�ky s� dostupn� pou�it�m
<function>stream_get_meta_data</function>.
</simpara>
<simpara>
- HTTP connections are read-only; you cannot write data or copy
- files to an HTTP resource.
+ Pripojenia cez HTTP s� iba na ��tanie; nem��ete zapisova� d�ta
+ alebo kop�rova� s�bory do HTTP zdroja.
</simpara>
<note>
- <simpara>HTTPS is supported starting from PHP 4.3, if you
- have compiled in support for OpenSSL.
+ <simpara>HTTPS podporovalo u� PHP 4.3, ak ste
+ kompilovali s podporou pre OpenSSL.
</simpara>
</note>
</section>
<section id="wrappers.ftp">
- <title>FTP and FTPS</title>
- <simpara>PHP 3, PHP 4. <filename>ftps://</filename> since PHP 4.3</simpara>
+ <title>FTP a FTPS</title>
+ <simpara>PHP 3, PHP 4. <filename>ftps://</filename> od PHP 4.3</simpara>
<itemizedlist>
<listitem><simpara><filename>ftp://example.com/pub/file.txt</filename></simpara></listitem>
@@ -64,37 +63,37 @@
</itemizedlist>
<simpara>
- Allows read access to existing files and creation of new files
- via FTP. If the server does not support passive mode ftp, the
- connection will fail.
- </simpara>
- <simpara>
- You can open files for either reading or writing, but not both
- simultaneously. If the remote file already exists on the ftp
- server and you attempt to open it for writing, the connection
- will fail. If you need to update existing files over ftp,
- use <function>ftp_connect</function>.
- </simpara>
- <simpara>
- <filename>ftps://</filename> was introduced in PHP 4.3.
- It is the same as <filename>ftp://</filename>,
- but attempts to negotiate a secure connection with the ftp server.
- If the server does not support SSL, then the connection falls back
- to regular unencrypted ftp.
+ Umo��uje pr�stup na ��tanie k existuj�cim s�borom a tvorbu
+ nov�ch cez FTP. Ak server nepodporuje pas�vny m�d ftp, spojenie
+ zlyh�.
+ </simpara>
+ <simpara>
+ M��te otv�ra� s�bory bu� na ��tanie alebo z�pis, ale nie oboje
+ z�rove�. Ak u� vzdialen� s�bor existuje na ftp serveri
+ a pok��ate sa ho otvori� na zapisovanie, spojenie zlyh�. Ak
+ potrebujete obnovi� existuj�ci s�bor cez ftp, pou�ite
+ <function>ftp_connect</function>.
+ </simpara>
+ <simpara>
+ <filename>ftps://</filename> bol predstaven� v PHP 4.3.
+ Je to rovnak� ako s <filename>ftp://</filename>,
+ ale pok��a sa vyh�ada� bezpe�n� spojenie s ftp serverom. Ak server
+ nepodporuje SSL, potom sa spojenie navr�ti k regul�rnemu
+ kryptovan�mu ftp.
</simpara>
<note>
- <simpara>FTPS is supported starting from PHP 4.3, if you
- have compiled in support for OpenSSL.
+ <simpara>FTPS podporovalo u� PHP 4.3, ak ste
+ kompilovali s podporou pre OpenSSL.
</simpara>
</note>
</section>
<section id="wrappers.php">
- <title>PHP input/output streams</title>
+ <title>Vstupn�/V�stupn� pr�dy PHP</title>
<simpara>
- PHP 3.0.13 and up, <filename>php://output</filename>
- and <filename>php://input</filename> since PHP 4.3
+ PHP 3.0.13 a vy��ie, <filename>php://output</filename>
+ a <filename>php://input</filename> po��naj�c PHP 4.3
</simpara>
<itemizedlist>
@@ -107,33 +106,33 @@
<simpara>
<filename>php://stdin</filename>, <filename>php://stdout</filename>
- and <filename>php://stderr</filename> allow access to
- the corresponding input or output stream of the PHP process.
+ a <filename>php://stderr</filename> umo��uj� pr�stup ku
+ kore�ponduj�cemu vstupn�mu alebo v�stupn�mu pr�du PHP procesu.
</simpara>
<simpara>
- <filename>php://output</filename> allows you to write to the
- output buffer mechanism in the same way as
- <function>print</function> and <function>echo</function>.
+ <filename>php://output</filename> umo��uje z�pis do v�stupn�ho
+ mechanizmu z�sobn�ka rovnak�m sp�sobom ako
+ <function>print</function> a <function>echo</function>.
</simpara>
<simpara>
- <filename>php://input</filename> allows you to read raw POST data.
- It is a less memory intensive alternative to
- <varname>$HTTP_RAW_POST_DATA</varname> and does not need any
- special &php.ini; directives.
+ <filename>php://input</filename> umo��uje ��tanie prvotn� POST d�ta.
+ Je to menej pam� za�a�uj�ca alternat�va k
+ <varname>$HTTP_RAW_POST_DATA</varname> a nepotrebuje �iadne
+ �peci�lne &php.ini; direkt�vy.
</simpara>
<simpara>
- <filename>php://stdin</filename> and
- <filename>php://input</filename> are read-only, whereas
+ <filename>php://stdin</filename> a
+ <filename>php://input</filename> s� iba na ��tanie, zatia��o
<filename>php://stdout</filename>,
- <filename>php://stderr</filename> and
- <filename>php://output</filename> are write-only.
+ <filename>php://stderr</filename> a
+ <filename>php://output</filename> s� iba na z�pis.
</simpara>
</section>
<section id="wrappers.compression">
- <title>Compression Streams</title>
- <simpara><filename>zlib:</filename> PHP 4.0.4 - PHP 4.2.3 (systems with fopencookie
only)</simpara>
- <simpara><filename>compress.zlib://</filename> and
<filename>compress.bzip2://</filename> PHP 4.3 and up</simpara>
+ <title>Pr�dy Kompresie</title>
+ <simpara><filename>zlib:</filename> PHP 4.0.4 - PHP 4.2.3 (iba syst�my s
+fopencookie)</simpara>
+ <simpara><filename>compress.zlib://</filename> a
+<filename>compress.bzip2://</filename> PHP 4.3 a vy��ie</simpara>
<itemizedlist>
<listitem><simpara><filename>zlib:</filename></simpara></listitem>
@@ -142,18 +141,18 @@
</itemizedlist>
<simpara>
- <filename>zlib:</filename> works like <function>gzopen</function>, except that the
- stream can be used with <function>fread</function> and the other
- filesystem functions. This is deprecated as of PHP 4.3 due
- to ambiguities with filenames containing ':' characters; use
- <filename>compress.zlib://</filename> instead.
+ <filename>zlib:</filename> pracuje ako <function>gzopen</function>, a� na to, �e
+ pr�d sa d� pou�i� s <function>fread</function> a in�mi
+ filesystem funkciami. Nie je to schva�ovan� ako to nie je aj v PHP 4.3
+ kv�li nejednozna�nosti s n�zvami s�borov obsahuj�cich znaky ':'; rad�ej
+ pou��vajte <filename>compress.zlib://</filename>.
</simpara>
<simpara>
- <filename>compress.zlib://</filename> and
- <filename>compress.bzip2://</filename> are equivalent to
- <function>gzopen</function> and <function>bzopen</function>
- respectively, and operate even on systems that do not support
+ <filename>compress.zlib://</filename> a
+ <filename>compress.bzip2://</filename> s� ekvivalentn� k
+ <function>gzopen</function> a <function>bzopen</function>
+ jednotlivo a funguj� dokonca aj na syst�moch, ktor� nepodporuj�
fopencookie.
</simpara>
</section>
Index: phpdoc/en/appendices/about.xml
diff -u phpdoc/en/appendices/about.xml:1.19 phpdoc/en/appendices/about.xml:1.20
--- phpdoc/en/appendices/about.xml:1.19 Sun Oct 27 07:31:14 2002
+++ phpdoc/en/appendices/about.xml Thu Dec 26 20:40:20 2002
@@ -1,161 +1,158 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.19 $ -->
+<?xml version="1.0" encoding="iso-8859-2"?>
+<!--EN-Revision: 1.19 Maintainer: joseph Status: ready -->
<!--
TODO: add manual conventions section (eg. how to read
function usage parts, what is fixed width, what is
- bold, what is linked
+ bold, what is linked)
add some tips about combining the versions (online-
offline), and using "http://anymirror.php.net/funcname";
-->
<appendix id="about">
- <title>About the manual</title>
+ <title>O manu�le</title>
<sect1 id="about.formats">
- <title>Formats</title>
+ <title>Form�ty</title>
<para>
- The PHP manual is provided in several formats. These formats can be divided
- into two groups: online readable formats, and downloadable packages.
+ PHP manu�l sa poskytuje v nieko�k�ch form�toch. Tieto form�ty sa delia
+ na dve skupiny: online �itate�n� form�ty a stiahnute�n� bal�ky.
</para>
<note>
<para>
- Some publishers have made available printed versions of this manual. We
- cannot recommend any of those, as they tend to become out-of-date very
- quickly.
+ Niektor� vyd�vatelia uviedli tla�en� verzie tohto manu�lu. Nem��eme
+ doporu�i� �iaden z nich, nako�ko s� zakr�tko zastaral�.
</para>
</note>
<para>
- You can read the manual online at <ulink url="&url.php;">&url.php;</ulink>
- and on the numerous mirror sites. For best performance, you should choose
- the mirror site closest to you. You can view the manual in either its plain
- (print-friendly) HTML format or an HTML format that integrates the manual
- into the look and feel of the PHP website itself.
+ Manu�l si m��ete pre��ta� online na <ulink url="&url.php;">&url.php;</ulink>
+ a na po�etn�ch mirrorovan�ch str�nkach. Pre najlep�iu �innos� by ste si mali
+ zvoli� mirrorovan� str�nku najbli��ie k v�m. Manu�l si m��ete prezera� bu�
+ v jednoduchom (vhodnom pre tla�) HTML form�te alebo v HTML form�te, ktor�
+ integruje manu�l do podoby samotnej webovskej str�nky PHP.
</para>
<para>
- An advantage of the online manual over most of the offline formats is the
- integration of <link linkend="about.notes">user-contributed
- notes</link>. An obvious disadvantage is that you have to be online to view
- the manual in the online formats.
+ V�hodou online manu�lu oproti v��ine offline form�tom je integr�cia
+ <link linkend="about.notes">pr�spevkov u�ivate�ov</link>. Zrejmou
+ nev�hodou je, �e mus�te by� online, aby ste si mohli prezera� manu�l
+ v online form�toch.
</para>
<para>
- There are several offline formats of the manual, and the most appropriate
- format for you depends on what operating system you use and your personal
- reading style. For information on how the manual is generated in so many
- formats, read the <link linkend="about.generate">'How we generate the
- formats'</link> section of this appendix.
+ Existuje nieko�ko offline form�tov manu�lu a fakt, ktor� form�t je pre v�s
+ najvhodnej��, z�vis� na opera�nom syst�me, ktor� pou��vate a osobnom
+ sp�sobe ��tania. Ak chcete vedie� ako sa tento manu�l generuje do mnoh�ch
+ form�tov, pre��tajte si sekciu <link linkend="about.generate">'Ako generujeme
+form�ty'</link> v tejto pr�lohe.
</para>
<para>
- The most cross-platform formats of the manual are the HTML and plain-text
- versions. The HTML format is provided both as a single HTML file and as
- a package of individual files for each section (which results in a
- collection of several thousand files). The HTML and plaintext formats are
- provided as tar files compressed using the bzip2 archiver.
+ Najvhodnej��mi multi-platformov�mi form�tmi manu�lu s� verzie HTML
+ a prost�-text. Form�t HTML sa poskytuje ako jednoduch� HTML s�bor ako aj
+ bal�k individu�lnych s�borov pre ka�d� sekciu (ktor� pozost�va zo zv�zku
+ nieko�ko tis�c s�borov). Form�ty HTML a prost�-text sa poskytuj� ako tar
+ s�bory komprimovan� programom bzip2.
</para>
<para>
- Another popular cross-platform format, and the format most suited to
- printing, is PDF (also known as Adobe Acrobat). But before you rush to
- download this format and hit the Print button, be warned that the manual is
- nearly 2000 pages long, and constantly being revised.
+ �al��m ob��ben�m multi-platformov�m form�tom, ktor� je najvhodnej�� pre
+ tla�, je PDF (tie� zn�my ako Adobe Acrobat). Ale ne� sa pust�te do
+ s�ahovania tohto form�tu a jeho tla�e, majte na pam�ti, �e manu�l m�
+ 2000 str�n a �e sa neust�le upravuje.
</para>
<note>
<para>
- If you do not already have a program capable of viewing PDF format
- files, you may need to download <ulink url="&url.adobe.acrobat;">Adobe
+ Ak e�te nem�te program schopn� prezerania s�borov form�tu PDF, mo�ete
+ si stiahn�� <ulink url="&url.adobe.acrobat;">Adobe
Acrobat Reader</ulink>.
</para>
</note>
<para>
- For owners of Palm-compatible handhelds, the Palm document and iSilo
- formats are ideal for this platform. You can bring your handheld with you
- on your daily commute and use a <ulink url="&url.palm.doc;">DOC</ulink>
- or <ulink url="&url.palm.isilo;">iSilo</ulink> reader to brush up on your
- PHP knowledge, or just use it as a quick reference.
+ Pre vlastn�kov handheldov kompaktibiln�ch s Palm s� ide�lne form�ty
+ Palm dokument a iSilo. M��ete si svoj handheld nosi� denne so sebou
+ a pou��va� <ulink url="&url.palm.doc;">DOC</ulink> alebo
+ <ulink url="&url.palm.isilo;">iSilo</ulink> reader, aby ste si
+ zdokonalili svoje PHP vedomosti, alebo ho len pou��va� ako pr�ru�ku.
</para>
<para>
- For Windows platforms, the Windows HTML Help version of the manual soups up
- the HTML format for use with the Windows HTML Help application. This
- version provides full-text search, a full index, and bookmarking. Many
- popular Windows PHP development environments also integrate with this
- version of the documentation to provide easy access.
+ Pre platformy Windows, verzia manu�lu Windows HTML Help umo��uje
+ pou�itie HTML form�tu vo Windows HTML Help aplik�ciach. T�to verzia
+ poskytuje full-textov� vyh�ad�vanie, pln� index, a ozna�nie zar�ok
+ (bookmarking). Mnoho zn�mych v�vojov�ch prostred� pre Windows tie�
+ zah��a t�to verziu dokument�cie pre jednoduch� pr�stup..
</para>
<!--
mmmm, this project seems to be dead. Any news?
<note>
<para>
- A Visual Basic for Linux project is in the planning stage, which will
- include the development of a CHM Creator and Viewer for Linux. See their
- <ulink url="&url.vb4linux;">SourceForge.net page</ulink> if you are
- interested in the progress.
+ Projekt Visual Basic pre Linux je pl�novan� f�za, ktor� bude zah��a�
+ v�voj CHM Creator and Wiewer pre Linux. Pozrite si ich na
+ <ulink url="&url.vb4linux;">str�nke SourceForge.net</ulink>, ak sa
+ zauj�mate o priebeh.
</para>
</note>
-->
</sect1>
<sect1 id="about.notes">
- <title>About user notes</title>
+ <title>O pr�spevkoch u��vate�ov</title>
<para>
- The user-contributed notes play an important role in the development of
- this manual. By allowing readers of the manual to contribute examples,
- caveats, and further clarifications from their browser, we are able to
- incorporate that feedback into the main text of the manual. And until the
- notes have been incorporated, they can be viewed in their submitted form
- online and in some of the offline formats.
+ Pr�spevky u�ivate�ov zohr�vaj� d�le�it� �lohu vo v�voji tohto manu�lu.
+ T�m, �e umo�n�me �itate�om manu�lu prispevanie pr�kladov, r�d a
+ �al��ch objasnen� z ich prehliada�a, ich m��eme za�leni� do hlavn�ho
+ textu manu�lu. K�m sa pr�spevky za�lenia, daj� sa prezera� vo svojej
+ predlo�enej forme online a v niektor�ch offline form�toch.
</para>
<note>
<para>
- The user-contributed notes are not moderated before they appear online, so
- the quality of the writing or code examples, and even the veracity of the
- contribution, cannot be guaranteed. (Not that there is any guarantee of
- the quality or accuracy of the manual text itself.)
+ Pr�spevky u��vate�ov, pred t�m ne� sa uverejnia online, nie s� upravovan�,
+ tak�e kvalita z�pisu alebo pr�kladov k�du, a dokonca ani spr�vnos�
+ pr�spevku sa nedaj� zaru�i�. (Taktie� nie je z�ruka kvality a presnosti
+ samotn�ho textu manu�lu.)
</para>
</note>
</sect1>
-
+
<sect1 id="about.prototypes">
- <title>How to read a function definition (prototype)</title>
+ <title>Ako ��ta� defin�ciu funkicie (prototyp)</title>
<para>
- Each function is documented for quick reference, knowing how
- to read and understand the manual will make using PHP
- much easier. Rather than relying on examples or cut/paste, you want
- to know how to read function definitions (prototypes). Let's begin:
+ Ka�d� funkcia je zdokumentovan� v informa�nej pr�ru�ke; znalos�,
+ ako sa m� manu�l ��ta� a rozumie�, pou��vanie PHP zna�ne
+ ulah��. Namiesto odvol�vania sa na pr�klady alebo vystrihn��/vlo�i�,
+ chcete rad�ej vedie� ako ��ta� defin�cie funkci� (prototypy). Za�nime:
</para>
<note>
<title>
- Prerequisite: Basic understanding of <link linkend="language.types">types</link>
+ Nevyhnutn� podmienka: Z�kladn� interpret�cia <link
+linkend="language.types">typov</link>
</title>
<para>
- Although PHP is a loosly typed language, it's important to have
- a basic understanding of <link linkend="language.types">types</link> as
- they have important meaning.
+ I ke� PHP je len po�ahky typov�m jazykom, je d�le�it� ma� z�kladn�
+ vedomosti o <link linkend="language.types">typoch</link>, preto�e
+ maj� d�le�it� v�znam.
</para>
</note>
<para>
- Function definitions tell us what
- type of value is <link linkend="functions.returning-values">returned</link>,
- let's use the definition for <function>strlen</function> as our first example:
+ Defin�cie funkci� n�m hovoria ak�
+ typ hodnoty je <link linkend="functions.returning-values">navr�ten�</link>,
+ pou�ijeme defin�ciu pre <function>strlen</function>, ako n� prv� pr�klad:
</para>
<para>
<screen role="html">
strlen
(PHP 3, PHP 4 >= 4.0.0)
-strlen -- Get string length
+strlen -- Ur�� d�ku reta�ca
-Description
+Popis
int strlen ( string str )
-Returns the length of string.
+Vr�ti d�ku re�azca.
</screen>
</para>
<para>
<table>
- <title>Explanation of a function definition</title>
+ <title>Vysvetlenie funk�nej defin�cie<title>
<tgroup cols="2">
<thead>
<row>
- <entry>Part</entry>
- <entry>Description</entry>
+ <entry>�as�</entry>
+ <entry>Popis</entry>
</row>
</thead>
<tbody>
@@ -164,7 +161,7 @@
strlen
</entry>
<entry>
- The function name.
+ N�zov funkcie.
</entry>
</row>
<row>
@@ -172,7 +169,7 @@
(PHP 3, PHP 4 >= 4.0.0)
</entry>
<entry>
- strlen() has been around in both all of PHP 3 and PHP 4
+ strlen() bol k dispoz�cii v ochoch PHP 3 a PHP 4
</entry>
</row>
<row>
@@ -180,9 +177,9 @@
int
</entry>
<entry>
- Type of value this function returns, which is an
+ Typ hodnoty, ktor� t�to funkcia vracia, �o je
<link linkend="language.types.integer">integer</link>
- (i.e. The length of a string is measured in numbers).
+ (t.j. D�ka re�azca sa ud�va v ��slach).
</entry>
</row>
<row>
@@ -190,9 +187,9 @@
( string str )
</entry>
<entry>
- The first (and in this case the only) parameter/argument for the
- function strlen() is named <parameter>str</parameter>, and it's a
- <link linkend="language.types.string">string</link>.
+ Prv� (a v tomto pr�pade jedin�) parameter/argument pre
+ funkciu strlen() sa naz�va <parameter>str</parameter> a je to
+ <link linkend="language.types.string">re�azec</link>.
</entry>
</row>
</tbody>
@@ -200,207 +197,204 @@
</table>
</para>
<para>
- We could rewrite the above function definition in a generic way:
+ Defin�ciu horeuvedenej funkcie by sme mohli prep�sa� do v�eobecn�ho tvaru:
</para>
<para>
<screen role="html">
- returned type function name ( parameter type parameter name )
+ vr�ten� typ n�zov funkcie ( typ parametra n�zov parametra )
</screen>
</para>
<para>
- Many functions take on multiple parameters, such as
<function>in_array</function>.
- It's prototype is as follows:
+ Mnoho funkci� m� viacero parametrov, ako m� napr. <function>in_array</function>.
+ Jeho prototyp vyzer� n�sledovne:
</para>
<para>
<screen role="html">
- bool in_array ( mixed needle, array haystack [, bool strict])
+ bool in_array ( zmie�an� ihla, array stoh_sena [, bool striktne])
</screen>
</para>
<para>
- What does this mean? in_array() returns a
- <link linkend="language.types.boolean">boolean</link> value, &true; on
- success (the <parameter>needle</parameter> was found in the
- <parameter>haystack</parameter>) or &false; on failure (the
- <parameter>needle</parameter> was not found in the
- <parameter>haystack</parameter>). The first parameter is named
- <parameter>needle</parameter> and it can be many different
- <link linkend="language.types">types</link>, so we call it
- "<emphasis>mixed</emphasis>". This mixed <parameter>needle</parameter>
- (what we're looking for) can either be a scalar value (string, integer,
- or <link linkend="language.types.float">float</link>), or an
- <link linkend="language.types.array">array</link>.
- <parameter>haystack</parameter> (the array we're searching in) is the
- second parameter. The third <emphasis>optional</emphasis> parameter is
- named <parameter>strict</parameter>. All optional parameters are seen
- in <emphasis>[</emphasis> brackets <emphasis>]</emphasis>. The manual
- states that the <parameter>strict</parameter> parameter defaults to
- boolean &false;. See the manual page on each function for details on
- how they work.
+ �o to vlastne znamen�? in_array() vracia hodnotu
+ <link linkend="language.types.boolean">boolean</link>, &true; ak je
+ prevdiv� (<parameter>ihla</parameter> bola n�jden� v
+ <parameter>stoh_sena</parameter>) alebo &false; pri chybe (
+ <parameter>ihla</parameter> sa nena�la v
+ <parameter>stoh_sena</parameter>). Prv� parameter je pomenovan�
+ <parameter>ihla</parameter> a m��e by� viacer�ch
+ <link linkend="language.types">typov</link>, tak�e sme ho nazvali
+ "<emphasis>zmie�an�</emphasis>". T�to zmie�an� <parameter>ihla</parameter>
+ (ktor� h�ad�me) mo�e by� bu� skal�rna hodnota (string, integer,
+ alebo <link linkend="language.types.float">float</link>) alebo
+ <link linkend="language.types.array">pole</link>.
+ <parameter>stoh_sena</parameter> (pole, v ktorom h�ad�me) je
+ druh� parameter. Tret� <emphasis>volite�n�</emphasis> parameter je
+ pomenovan� <parameter>striktne</parameter>. V�etky volite�n� parametre s�
+uzavret�
+ do <emphasis>[</emphasis> z�tvoriek <emphasis>]</emphasis>. Manu�l
+ uklad�, �e parameter <parameter>striktne</parameter> je �tandardne
+ nasteven� na boolean &false;. Pozri manu�lov� str�nku pre ka�d�
+ funkciu a ako funguj�.
</para>
</sect1>
<sect1 id="about.phpversions">
- <title>PHP versions documented in this manual</title>
+ <title>Verzie PHP zdokumentovan� v tomot manu�le</title>
<para>
- This documentation contains information about PHP 4, with some added
- migration and compatibility notes regarding PHP 3. Behaviour,
- parameter, return value and other changes between different PHP
- versions are documented in notes and inline text in the manual.
- </para>
- <para>
- You may find documentation pieces for the CVS version of PHP, which
- always means the very latest development version available through
- the CVS version handling system. If you are not a developer of PHP
- itself, and you are not keen on using the very latest development
- version of PHP, features marked with the "available in CVS" wording
- are not accessible to you. Though these features will probably be
- available in the next stable version of PHP. If you would like to
- download the CVS version, see the <ulink url="&url.php.anoncvs;">anonymous
- CVS access page</ulink>.
- </para>
- <para>
- You may also encounter documentation for a PHP version which is
- not released (something like PHP 4.3.0 as the latest stable version
- is 4.2.3). Most of the time, this is not an error in the documentation.
- Explanation is often added for features not available in the current
- PHP release, but will be available in a known future PHP version.
+ T�to dokument�cia obsahuje inform�cie o PHP 4, s niektor�mi pridan�mi
+ migr�ciami a pozn�mkami ku kompatibilite s PHP 3. Spr�vanie,
+ parameter, navr�tenie hodnoty a in� zmeny medzi r�znymi verziami
+ PHP s� zdokumentovan� v pozn�mkach a v medziriadkovom texte v manu�le.
+ </para>
+ <para>
+ M��te n�js� dokumenta�n� k�sky pre CVS verziu PHP, ktor� v�dy
+ predstavuje najnov�ie vyv�jan� verziu dostupn� cez syst�m CVS. Ak
+ nie ste v�voj�rom PHP samotn�ho a nie ste nad�en� pou��van�m
+ najnov�ie vyv�janej verzie PHP, rubriky ozna�en� "available in CVS"
+ (dostupn� v CVS) nie s� pre v�s dostupn�. I ke� tieto rubriky bud�
+ prevdepodobne dostupn� v dal�ej samostatnej verzii PHP. Ak by ste
+ si chceli stiahnu� CVS verziu, pozri <ulink url="&url.php.anoncvs;">anonymn�
+pr�stupn� CVS str�nka</ulink>.
+ </para>
+ <para>
+ Taktie� m��te narazi� na dokument�ciu pre PHP verziu, ktor� e�te
+ nie je uvo�nen� (nie�o ako PHP 4.3.0, preto�e najnov�ia samostatn�
+ verzia je 4.2.3). V��inou toto nepredstavuje chybu v dokumt�cii.
+ Vysvetlenie sa �asto prid�va k rubrik�m, ktor� nie s� dostupn� v
+ aktu�lnom PHP vydan�, ale bud� dostupn� v zn�mej bud�cej PHP verzi�.
</para>
</sect1>
-
+
<sect1 id="about.more">
- <title>How to find more information about PHP</title>
+ <title>Ako n�js� viac inform�cii o PHP</title>
<para>
- This manual does not attempt to provide instruction about general
- programming practices. If you are a first-time, or even just a beginning,
- programmer, you may find it difficult to learn how to program in PHP using
- just this manual. You may want to seek out a text more oriented towards
- beginners. You can find a list of PHP-related books at <ulink
+ Tento manu�l sa nesna�� poskytova� in�trukcie o v�eobecn�ch programovac�ch
+ praktik�ch. Ak ste len za��naj�cim program�torom, m��e sa v�m zda� zlo�it�
+ nau�i� sa programova� v PHP len za pomoci tohto manu�lu. M��ete si
+ vyh�ada� texty, ktor� s� viac orientovan� pre za�iato�n�kov. Zoznam
+ kn�h s�visiacich s PHP m��ete n�js� na <ulink
url="&url.php.books;">&url.php.books;</ulink>.
</para>
<para>
- There are a number of active mailing lists for discussion of all aspects of
- programming with PHP. If you find yourself stuck on a problem for which you
- can't find your own solution, you may be able to get help from someone on
- these lists. You can find a list of the mailing lists at <ulink
- url="&url.php.support;">&url.php.support;</ulink>, as well as links to the
- mailing list archives and other online support resources. Furthermore, at
- <ulink url="&url.php.links;">&url.php.links;</ulink> there is a list of
- websites devoted to PHP articles, forums, and code galleries.
+ Existuje mno�stvo akt�vnych mailing listov ur�en�ch pre diskusie o v�etk�ch
+ aspektoch programovania v PHP. Ak ste uviazli na probl�me, na ktor� neviete
+ n�js� vlastn� rie�enie, m��ete z�ska� pomoc od niekoho na t�chto mailing
+ listoch. Zoznam mailing listov rovnako ako liniek na arch�vy mailing listov
+ a in�ch podporn�ch online zdrojov m��ete n�js� na <ulink
+ url="&url.php.support;">&url.php.support;</ulink>.
+ Okrem toho, na
+ <ulink url="&url.php.links;">&url.php.links;</ulink> je zoznam webov�ch
+ str�nok ur�en�ch PHP �l�nkom, diskusn�m f�ram a gal�ri�m k�dov.
</para>
</sect1>
<sect1 id="about.howtohelp">
- <title>How to help improve the documentation</title>
+ <title>Ako pom�c� pri zlep�ovan� dokument�cie</title>
<para>
- There are three ways you can help to improve this documentation.
+ S� tri sp�soby ako m��ete pom�c� zlep�i� t�to dokument�ciu.
</para>
<para>
- If you find errors in this manual, in any language, please report them
- using the bug system at <ulink url="&url.php.bugs;">&url.php.bugs;</ulink>.
- Classify the bug as "Documentation Problem". You can also submit problems
- related to specific manual formats here.
+ Ak v tomto manu�li n�jdete chyby, i v inom jazyku, pros�m hl�ste ich
+ pomocou bug syst�mu na <ulink url="&url.php.bugs;">&url.php.bugs;</ulink>.
+ Klasifikujte bug ako "Documentation Problem". M��ete tu tie� hl�si�
+ probl�my, ktor� s�visia so �pecifick�m form�tom manu�lu.
</para>
<note>
<para>
- Please don't abuse the bug system by submitting requests for help. Use the
- mailing lists or community sites mentioned earlier, instead.
+ Pros�m, nezneu��vajte bug syst�m �iadan�m o pomoc. Namiesto toho pou��vajte
+ sk�r spomenut� mailing listy alebo str�nky komunity.
</para>
</note>
<para>
- By contributing notes, you can provide additional examples, caveats, and
- clarifications for other readers. But do not submit bug reports using the
- annotation system please. You can read more about annotations in the <link
- linkend="about.notes">'About user notes'</link> section of this
- appendix.
+ Prispievan�m pozn�mok m��ete poskytova� dopl�uj�ce pr�klady, rady a
+ objasnenia pre in�ch �itate�ov. Ale, pros�m, nepod�vajte bug reporty
+ pou�it�m anota�n�ho syst�mu. O anot�ci�ch si m��ete pre��ta� viac v sekcii
+ <link linkend="about.notes">'O pr�spevkoch u��vate�ov'</link> tejto pr�lohy.
</para>
<para>
- If you know English and some foreign language, you may also
- help out in the translations. If you would like to start a new
- translation, or help in a translation project, please read
+ Ak viete anglicky a nejak� cudz� jazyk, m��ete taktie� vypom�c�
+ v prekladan�. Ak by ste chceli za�a� nov� preklad, alebo
+ pom�c� v projekte prekladu, pros�m ��tajte
<ulink url="&url.php.dochowto;">&url.php.dochowto;</ulink>.
</para>
</sect1>
<sect1 id="about.generate">
- <title>How we generate the formats</title>
+ <title>Ako generujeme form�ty</title>
<para>
- This manual is written in <acronym>XML</acronym> using the <ulink
- url="&url.docbook.xml;">DocBook XML DTD</ulink>, using <ulink
- url="&url.dsssl;"><acronym>DSSSL</acronym></ulink> (Document
- Style and Semantics Specification Language) for formatting, and
- experimentally the <ulink url="&url.xslt;"><acronym>XSLT</acronym>
+ Tento manu�l je nap�san� v <acronym>XML</acronym> pomocou
+ <ulink url="&url.docbook.xml;">DocBook XML DTD</ulink>, vyu��vaj�ci
+ <ulink url="&url.dsssl;"><acronym>DSSSL</acronym></ulink> (Document
+ Style and Semantics Specification Language) pre form�tovanie a
+ experimentr�lne <ulink url="&url.xslt;"><acronym>XSLT</acronym>
</ulink> (Extensible Stylesheet Language Transformations)
- for maintenance and formatting.
+ pre �pravu a form�tovanie.
</para>
<para>
- Using <acronym>XML</acronym> as a source format gives us
- the ability to generate many output formats from the source
- files, while only maintaining one source document for all formats.
- The tools used for formatting <acronym>HTML</acronym> and
- <acronym>TeX</acronym> versions are
- <ulink url="&url.jade;">Jade</ulink>, written by <ulink
- url="&url.jclark;">James Clark</ulink> and <ulink
- url="&url.dbstyle;">The Modular DocBook Stylesheets</ulink>
- written by <ulink url="&url.nwalsh;">Norman Walsh</ulink>.
- We use <ulink url="&url.winhelp;">Microsoft HTML Help
- Workshop</ulink> to generate the Windows HTML Help format
- of the manual, and of course PHP itself to do some
- additional conversions and formatting.
- </para>
- <para>
- You can download the manual in various languages and
- formats, including plain text, plain <acronym>HTML</acronym>,
- <acronym>PDF</acronym>, PalmPilot DOC, PalmPilot iSilo and
- Windows HTML Help, from
+ Pou��vanie <acronym>XML</acronym> ako zdrojov�ho form�tu n�m
+ umo��uje generovanie mnoh�ch v�stupn�ch form�tov zo zdrojov�ch
+ s�borov, pri�om sa upravuje iba jeden zdrojov� dokument pre v�etky
+ form�ty. N�stroje pou��van� na form�tovanie <acronym>HTML</acronym>
+ a <acronym>TeX</acronym> verzi� s�
+ <ulink url="&url.jade;">Jade</ulink>, ktor� nap�sal <ulink
+ url="&url.jclark;">James Clark</ulink> a <ulink
+ url="&url.dbstyle;">The Modular DocBook Stylesheets</ulink>,
+ ktor� nap�sal <ulink url="&url.nwalsh;">Norman Walsh</ulink>.
+ Pou��vame <ulink url="&url.winhelp;">Microsoft HTML Help
+ Workshop</ulink>, aby sme vygenerovali form�t Windows HTML Help
+ manu�lu a, samozrejme, samotn� PHP, aby sme urobili
+ dodato�n� �pravy a form�tovanie.
+ </para>
+ <para>
+ Tie� si manu�l m��ete stiahn�� vo viacer�ch jazykoch
+ a form�tch, vr�tanie prost�ho textu, <acronym>HTML</acronym>,
+ <acronym>PDF</acronym>, PalmPilot DOC, PalmPilot iSilo a
+ Windows HTML Help, z
<ulink url="&url.php.docs;">&url.php.docs;</ulink>.
- The manuals are updated automatically as the text is updated.
+ Manu�ly sa aktualizuj� automaticky s��asne s textom.
</para>
<para>
- You can find more information about downloading the
- <acronym>XML</acronym> source code of this documentation
- at <ulink url="&url.php.cvs;">&url.php.cvs;</ulink>. The
- documentation is stored in the <literal>phpdoc</literal> module.
+ Viac inform�ci� o s�ahovan� zdrojov�ho k�du
+ <acronym>XML</acronym> tejto dokument�cie m��ete n�js�
+ na <ulink url="&url.php.cvs;">&url.php.cvs;</ulink>.
+ Dokument�cia je ulo�en� v module <literal>phpdoc</literal>.
</para>
</sect1>
<sect1 id="about.translations">
- <title>Translations</title>
+ <title>Preklady</title>
<para>
- The PHP manual is not only available in various formats,
- it is also available in various languages. The text of the
- manual is first written in english, then teams of people across
- the world take care of translating it to their native language.
- If a translation for a specified function or chapter has not yet
- been made, the build system of the manual falls back to the
- english version of it.
- </para>
- <para>
- Peoples involved in the translations start from the <acronym>XML</acronym>
- source code available from <ulink url="&url.php.cvs;">&url.php.cvs;</ulink>
- and from it they translate to thier mother language. They do
- <emphasis>not use</emphasis> the <acronym>HTML</acronym>, the plain text,
- or the <acronym>PDF</acronym> version. It is the build system which takes
- care of the conversions from <acronym>XML</acronym> to human readable formats.
+ PHP manu�l je dostupn� nie len vo viacer�ch form�toch,
+ ale tie� vo viacer�ch jazykoch. Text manu�lu sa najsk�r
+ nap��e v angli�tine a potom ho t�my �ud� po celom svete
+ prekladaj� do svojho rodn�ho jazyka. Ak sa preklad pre
+ �pecifick� funkciu alebo kapitolu e�te neurobil, build syst�m
+ manu�lu spad� do svojej anglickej verzie.
+ </para>
+ <para>�
+ �udia, ktor� sa podie�aj� na prekladoch za��naj� zo zdrojov�ho k�du
+ <acronym>XML</acronym> dostupn�ho na <ulink
+url="&url.php.cvs;">&url.php.cvs;</ulink>
+ a z neho ho prekladaj� do svojho materinsk�ho jazyka.
+ <emphasis>Nepou��vaj�</emphasis> <acronym>HTML</acronym>, prost� text,
+ ani <acronym>PDF</acronym> verziu. Je to build syst�m, ktor� preklad�
+ <acronym>XML</acronym> k�d do �udskej re�i.
</para>
<note>
<para>
- If you would like to help translating the documentation to your native
- language, please get in touch with the translation/documentation team
- subscribing to the phpdoc mailinglist: send an empty mail to <ulink
+ Ak by ste sa chceli podiela� na prekladan� dokument�cie do v�ho
+ rodn�ho jazyka, pros�m, kontaktujte translation/documentation team
+ prihlasen�m sa do mailing listu phpdoc: po�lite pr�zdny mail na <ulink
url="mailto:&email.php.doc.subscribe;";>&email.php.doc.subscribe;</ulink>.
- The mailing list address is <literal>&email.php.doc;</literal>. State in the
- message that you are interested in translating the manual to a language
- and someone will get back to you, helping you start a new language translation
- or reach the already active documentation team for your language.
- </para>
+ Adresa mailing listu je <literal>&email.php.doc;</literal>. V spr�ve
+ uve�e, �e m�te z�ujem o prekladanie manu�lu do svojho jazyka. Niekto sa
+ v�m ozve, radiac v�m ako za�a� preklad do nov�ho jazyka alebo ako sa
+ pripoji� k u� akt�vnemu dokumenta�n�mu t�mu pre v� jazyk.
+ </para>
</note>
<para>
- At the moment the manual is available, partly or not, in the following languages:
- Brazilian Portuguese, Chinese, Czech, Dutch, French, German, Hungarian, Italian,
- Japanese, Korean, Polish and Spanish.
+ Moment�lne je manu�l �iasto�ne dostupn� v n�sleduj�cich jazykoch:
+ v braz�lskej portugal�tine, ��n�tine, �e�tine, holand�tine, franc�z�tine,
+ nem�ine, ma�ar�ine, talian�ine, japon�ine, k�rej�ine, pol�tine a �paniel�ine.
</para>
<para>
- They all can be downloaded here: <ulink
url="&url.php.docs;">&url.php.docs;</ulink>.
+ V�etky sa daj� stiahn�� tu: <ulink url="&url.php.docs;">&url.php.docs;</ulink>.
</para>
</sect1>
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
