jmcastagnetto           Thu Dec 26 23:40:54 2002 EDT

  Modified files:              
    /phpdoc/en/appendices       about.xml 
  Log:
  Reverting to a sane version of the file, and adding the info about the
  user-contributed notes being covered by the same license as the manual,
  becuase they are part of it.
  
  
Index: phpdoc/en/appendices/about.xml
diff -u phpdoc/en/appendices/about.xml:1.20 phpdoc/en/appendices/about.xml:1.21
--- phpdoc/en/appendices/about.xml:1.20 Thu Dec 26 20:40:20 2002
+++ phpdoc/en/appendices/about.xml      Thu Dec 26 23:40:54 2002
@@ -1,158 +1,170 @@
-<?xml version="1.0" encoding="iso-8859-2"?>
-<!--EN-Revision: 1.19 Maintainer: joseph Status: ready -->
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!-- $Revision: 1.21 $ -->
 
 <!--
   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>O manu�le</title>
+ <title>About the manual</title>
 
  <sect1 id="about.formats">
-  <title>Form�ty</title>
+  <title>Formats</title>
   <para>
-   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.
+   The PHP manual is provided in several formats. These formats can be divided
+   into two groups: online readable formats, and downloadable packages.
   </para>
   <note>
    <para>
-    Niektor� vyd�vatelia uviedli tla�en� verzie tohto manu�lu. Nem��eme 
-    doporu�i� �iaden z nich, nako�ko s� zakr�tko zastaral�.
+    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.
    </para>
   </note>
   <para>
-   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.
+   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.
   </para>
   <para>
-   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.
+   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.
   </para>
   <para>
-   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.
+   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.
   </para>
   <para>
-   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.
+   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.
   </para>
   <para>
-   �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.
+   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.
   </para>
   <note>
    <para>
-    Ak e�te nem�te program schopn� prezerania s�borov form�tu PDF, mo�ete
-    si stiahn�� <ulink url="&url.adobe.acrobat;">Adobe
+    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
     Acrobat Reader</ulink>.
    </para>
   </note>
   <para>
-   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.
+   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.
   </para>
   <para>
-   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..
+   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.
   </para>
 <!--
   mmmm, this project seems to be dead. Any news?
   <note>
    <para>
-    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.
+    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.
    </para>
   </note>
   -->
  </sect1>
  
  <sect1 id="about.notes">
-  <title>O pr�spevkoch u��vate�ov</title>
+  <title>About user notes</title>
   <para>
-   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.
+   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.
   </para>
   <note>
    <para>
-    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.)
+    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.)
+   </para>
+  </note>
+  <note>
+   <para>
+    For the purposes of license coverage the user-contributed notes are
+    considered part of the PHP manual, and are therefore covered by the
+    same license that covers this documentation (GPL at the moment). For
+    more details see the <link linkend="copyright">Manual's Copyright</link>
+    page.
    </para>
   </note>
  </sect1>
- 
+
  <sect1 id="about.prototypes">
-   <title>Ako ��ta� defin�ciu funkicie (prototyp)</title>
+   <title>How to read a function definition (prototype)</title>
    <para>
-    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:
+    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:
    </para>
    <note>
     <title>
-     Nevyhnutn� podmienka: Z�kladn� interpret�cia <link 
linkend="language.types">typov</link>
+     Prerequisite: Basic understanding of <link linkend="language.types">types</link>
     </title>
     <para>
-     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.
+     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.
     </para>
    </note>
    <para>
-    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:
+    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:
    </para>
    <para>
     <screen role="html">
 strlen
 
 (PHP 3, PHP 4 >= 4.0.0)
-strlen -- Ur�� d�ku reta�ca
+strlen -- Get string length
 
-Popis
+Description
 int strlen ( string str )
 
-Vr�ti d�ku re�azca.
+Returns the length of string.
     </screen>
    </para>
    <para>
     <table>
-     <title>Vysvetlenie funk�nej defin�cie<title>
+     <title>Explanation of a function definition</title>
       <tgroup cols="2">
        <thead>
         <row>
-         <entry>�as�</entry>
-         <entry>Popis</entry>
+         <entry>Part</entry>
+         <entry>Description</entry>
         </row>
        </thead>
        <tbody>
@@ -161,7 +173,7 @@
           strlen
          </entry>
          <entry>
-          N�zov funkcie.
+          The function name.
          </entry>
         </row>
         <row>
@@ -169,7 +181,7 @@
           (PHP 3, PHP 4 >= 4.0.0)
          </entry>
          <entry>
-          strlen() bol k dispoz�cii v ochoch PHP 3 a PHP 4
+          strlen() has been around in both all of PHP 3 and PHP 4
          </entry>
         </row>
         <row>
@@ -177,9 +189,9 @@
           int
          </entry>
          <entry>
-          Typ hodnoty, ktor� t�to funkcia vracia, �o je 
+          Type of value this function returns, which is an 
           <link linkend="language.types.integer">integer</link>
-          (t.j. D�ka re�azca sa ud�va v ��slach).
+          (i.e. The length of a string is measured in numbers).
          </entry>
         </row>
         <row>
@@ -187,9 +199,9 @@
           ( string str )
          </entry>
          <entry>
-          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>.
+          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>.
          </entry>
         </row>
        </tbody>
@@ -197,204 +209,207 @@
      </table>
     </para>
     <para>
-     Defin�ciu horeuvedenej funkcie by sme mohli prep�sa� do v�eobecn�ho tvaru:
+     We could rewrite the above function definition in a generic way:
     </para>
     <para>
      <screen role="html">
-      vr�ten� typ    n�zov funkcie    ( typ parametra   n�zov parametra )
+      returned type    function name    ( parameter type   parameter name )
      </screen>
     </para>
     <para>
-     Mnoho funkci� m� viacero parametrov, ako m� napr. <function>in_array</function>.
-     Jeho prototyp vyzer� n�sledovne:
+     Many functions take on multiple parameters, such as 
+<function>in_array</function>.
+     It's prototype is as follows:
     </para>
     <para>
      <screen role="html">    
-      bool in_array ( zmie�an� ihla, array stoh_sena [, bool striktne])
+      bool in_array ( mixed needle, array haystack [, bool strict])
      </screen>
     </para>
     <para>
-     �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�.
+     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.
     </para>
  </sect1>
  
  <sect1 id="about.phpversions">
-  <title>Verzie PHP zdokumentovan� v tomot manu�le</title>
+  <title>PHP versions documented in this manual</title>
   <para>
-   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�.
+   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.
   </para>
  </sect1>
-
+   
  <sect1 id="about.more">
-  <title>Ako n�js� viac inform�cii o PHP</title>
+  <title>How to find more information about PHP</title>
   <para>
-   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
+   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
    url="&url.php.books;">&url.php.books;</ulink>.
   </para>
   <para>
-   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.
+   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.
   </para>
  </sect1>
 
  <sect1 id="about.howtohelp">
-  <title>Ako pom�c� pri zlep�ovan� dokument�cie</title>
+  <title>How to help improve the documentation</title>
   <para>
-   S� tri sp�soby ako m��ete pom�c� zlep�i� t�to dokument�ciu.
+   There are three ways you can help to improve this documentation.
   </para>
   <para>
-   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.
+   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.
   </para>
   <note>
    <para>
-    Pros�m, nezneu��vajte bug syst�m �iadan�m o pomoc. Namiesto toho pou��vajte
-    sk�r spomenut� mailing listy alebo str�nky komunity.
+    Please don't abuse the bug system by submitting requests for help. Use the
+    mailing lists or community sites mentioned earlier, instead.
    </para>
   </note>
   <para>
-   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.
+   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.
   </para>
   <para>
-   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 
+   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
    <ulink url="&url.php.dochowto;">&url.php.dochowto;</ulink>.
   </para>
  </sect1>
  
  <sect1 id="about.generate">
-  <title>Ako generujeme form�ty</title>
+  <title>How we generate the formats</title>
   <para>
-   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>
+   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>
    </ulink> (Extensible Stylesheet Language Transformations)
-   pre �pravu a form�tovanie.
+   for maintenance and formatting.
   </para>
   <para>
-   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
+   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
    <ulink url="&url.php.docs;">&url.php.docs;</ulink>.
-   Manu�ly sa aktualizuj� automaticky s��asne s textom.
+   The manuals are updated automatically as the text is updated.
   </para>
   <para>
-   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>.
+   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.
   </para>
  </sect1>
 
  <sect1 id="about.translations">
-  <title>Preklady</title>
+  <title>Translations</title>
   <para>
-   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.
+   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.
   </para>
   <note>
    <para>
-    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
+    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
     url="mailto:&email.php.doc.subscribe;";>&email.php.doc.subscribe;</ulink>.
-    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>
+    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>    
   </note>
   <para>
-   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.
+   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.
   </para>
   <para>
-   V�etky sa daj� stiahn�� tu: <ulink url="&url.php.docs;">&url.php.docs;</ulink>.
+   They all can be downloaded here: <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

Reply via email to