cvs: phpdoc-cs /chapters tutorial.xml /docweb main.ent

From: Date: Tue, 22 Feb 2005 20:41:11 +0000
Subject: cvs: phpdoc-cs /chapters tutorial.xml /docweb main.ent
Groups: php.doc.cs 
Request: Send a blank email to doc-cs+get-146@lists.php.net to get a copy of this message
luk Tue Feb 22 15:41:11 2005 EDT Added files: /phpdoc-cs/chapters tutorial.xml /phpdoc-cs/docweb main.ent Log: New translated files

http://cvs.php.net/co.php/phpdoc-cs/chapters/tutorial.xml?r=1.1&p=1 Index: phpdoc-cs/chapters/tutorial.xml +++ phpdoc-cs/chapters/tutorial.xml <?xml version="1.0" encoding="iso-8859-2"?> <!-- EN-Revision: 1.37 Maintainer: luk Status: mixed --> <chapter id="tutorial"> <title>Struèný tutoriál</title> <para> Rádi bychom zde ukázali naprosté základy PHP v krátkém, jednoduchém tutoriálu. Tento text se zabývá jen dynamickým generování WWW stránek pomocí PHP, pøesto¾e PHP umí mnohem více ne¾ pouze toto. Více informací - viz sekce s názvem <link linkend="intro-whatcando">Co doká¾e PHP</link>. </para> <para> S webovými stránkami s PHP se zachází jako s normálními HTML stránkami a mù¾ete je vytváøet a upravovat stejným zpùsobem, jako kdy¾ vytváøíte bì¾né HTML stránky. </para> <sect1 id="tutorial.requirements"> <title>Co potøebuji?</title> <para> V tomto tutoriálu se pøedpokládá, ¾e vá¹ server má aktivovánu podporu PHP a ¾e v¹echny soubory konèící na <filename>.php</filename> jsou obslou¾eny pomocí PHP. Na vìt¹inì serverù je to výchozí nastavení pro PHP soubory, ale pro jistotu se zeptejte správce serveru. Podporuje-li vá¹ server PHP, nebudete potøebovat nic dìlat. Pouze vytvoøte své <filename>.php</filename> soubory, vlo¾te je do webového adresáøe a server je bude pro vás automaticky parsovat. Není nutné cokoli kompilovat ani instalovat nìjaké zvlá¹tní nástroje. Uva¾ujte o PHP souborech jako o jednoduchých HTML souborech s celou novou rodinou magických znaèek, které umo¾òují dìlat celou øadu vìcí. Vìt¹ina webových hostingù nabízí podporu PHP, ale pokud ten vá¹ nikoli, zva¾te pøeètení sekce <ulink url="&url.php.links;">PHP odkazù</ulink> pro prostøedky k nalezení vhodného hostingu. </para> <para> Øeknìme, ¾e chcete u¹etøit drahocenné pøenosové pásmo a vyvíjet místnì (na va¹em poèítaèi). V takovém pøípadì budete chtít nainstalovat webserver, napøíklad <ulink url="&url.apache;">Apache</ulink>, a samozøejmì <ulink url="&url.php.downloads;">PHP</ulink>. Vìt¹inou budete chtít instalovat také databázi, kupøíkladu <ulink url="&url.mysql.docs;">MySQL</ulink>. </para> <para> Tyto mù¾ete instalovat individuálnì nebo zvolit jednodu¹¹í cestu. Ná¹ manuál má <link linkend="install">instrukce pro instalaci PHP</link> (pøedpokládající, ¾e u¾ máte nainstalován webserver). Máte-li problémy s instalací samotného PHP, doporuèujeme polo¾it otázku na na¹em <ulink url="&url.php.mailing-lists;">instalaèním e-mailovém fóru</ulink>. Zvolíte-li jednodu¹¹í cestu, potom <ulink url="&url.installkits;">najdìte pøedkonfigurovaný balíèek</ulink> pro vá¹ operaèní systém, který na pár kliknutí my¹í v¹echno automaticky nainstaluje. Je snadné nainstalovat webserver s podporou PHP na jakýkoli operaèní systém, vèetnì Mac OS X, Linuxu a Windows. Na Linuxu mohou být k nalezení balíkù u¾iteèné <ulink url="&url.rpmfind;">rpmfind</ulink> a <ulink url="&url.rpmfind.pbone;">PBone</ulink>. Mù¾ete také nav¹tívit <ulink url="&url.apt-get;">apt-get</ulink> pro nalezení balíkù pro Debian. </para> </sect1> <sect1 id="tutorial.firstpage"> <title>Va¹e první stránka v PHP</title> <para> Vytvoøte soubor nazvaný <filename>hello.php</filename> a vlo¾te ho do koøenového adresáøe va¹eho webserveru (<varname>DOCUMENT_ROOT</varname>). Soubor bude mít následující obsah: </para> <para> <example> <title>Ná¹ první PHP skript: <filename>hello.php</filename></title> <programlisting role="php"> <![CDATA[ <html> <head> <title>PHP Test</title> </head> <body> <?php echo '<p>Ahoj svìte</p>'; ?> </body> </html> ]]> </programlisting> <simpara> Pro pøístupu k souboru pou¾ijte vá¹ webový prohlí¾eè, zadejte do nìj URL serveru zakonèený "/hello.php" (odkazem na soubor). Vyvíjíte-li lokálnì, bude URL nìco jako <literal>http://localhost/hello.php</literal> nebo <literal>http://127.0.0.1/hello.php</literal>, ale zále¾í to na konfiguraci serveru. Je-li v¹echno nakonfigurováno správnì, soubor bude parsován interpretem PHP a ten po¹le do va¹eho prohlí¾eèe tato data: </simpara> <screen role="html"> <![CDATA[ <html> <head> <title>PHP Test</title> </head> <body> <p>Ahoj svìte</p> </body> </html> ]]> </screen> </example> </para> <para> This program is extremely simple and you really did not need to use PHP to create a page like this. All it does is display: <literal>Hello World</literal> using the PHP <function>echo</function> statement. Note that the file <emphasis>does not need to be executable</emphasis> or special in any way. The server finds out that this file needs to be interpreted by PHP because you used the ".php" extension, which the server is configured to pass on to PHP. Think of this as a normal HTML file which happens to have a set of special tags available to you that do a lot of interesting things. </para> <para> If you tried this example and it did not output anything, it prompted for download, or you see the whole file as text, chances are that the server you are on does not have PHP enabled, or is not configured properly. Ask your administrator to enable it for you using the <link linkend="install">Installation</link> chapter of the manual. If you are developing locally, also read the installation chapter to make sure everything is configured properly. Make sure that you access the file via http with the server providing you the output. If you just call up the file from your file system, then it will not be parsed by PHP. If the problems persist anyway, do not hesitate to use one of the many <ulink url="&url.php.support;">PHP support</ulink> options. </para> <para> The point of the example is to show the special PHP tag format. In this example we used <literal>&lt;?php</literal> to indicate the start of a PHP tag. Then we put the PHP statement and left PHP mode by adding the closing tag, <literal>?&gt;</literal>. You may jump in and out of PHP mode in an HTML file like this anywhere you want. For more details, read the manual section on the <link linkend="language.basic-syntax"> basic PHP syntax</link>. </para> <note> <title>A Note on Text Editors</title> <para> There are many text editors and Integrated Development Environments (IDEs) that you can use to create, edit and manage PHP files. A partial list of these tools is maintained at <ulink url="&url.phpeditorlist;">PHP Editors List</ulink>. If you wish to recommend an editor, please visit the above page and ask the page maintainer to add the editor to the list. Having an editor with syntax highlighting can be helpful. </para> </note> <note> <title>A Note on Word Processors</title> <para> Word processors such as StarOffice Writer, Microsoft Word and Abiword are not optimal for editing PHP files. If you wish to use one for this test script, you must ensure that you save the file as <emphasis>plain text</emphasis> or PHP will not be able to read and execute the script. </para> </note> <note> <title>A Note on Windows Notepad</title> <para> If you are writing your PHP scripts using Windows Notepad, you will need to ensure that your files are saved with the .php extension. (Notepad adds a .txt extension to files automatically unless you take one of the following steps to prevent it.) When you save the file and are prompted to provide a name for the file, place the filename in quotes (i.e. "<filename>hello.php</filename>"). Alternatively, you can click on the 'Text Documents' drop-down menu in the 'Save' dialog box and change the setting to "All Files". You can then enter your filename without quotes. </para> </note> <para> Now that you have successfully created a working PHP script, it is time to create the most famous PHP script! Make a call to the <function>phpinfo</function> function and you will see a lot of useful information about your system and setup such as available <link linkend="language.variables.predefined">predefined variables</link>, loaded PHP modules, and <link linkend="configuration">configuration</link> settings. Take some time and review this important information. </para> <para> <example> <title>Get system information from PHP</title> <programlisting role="php"> <![CDATA[ <?php phpinfo(); ?> ]]> </programlisting> </example> </para> </sect1> <sect1 id="tutorial.useful"> <title>Nìco u¾iteèného</title> <para> Let us do something more useful now. We are going to check what sort of browser the visitor is using. For that, we check the user agent string the browser sends as part of the HTTP request. This information is stored in a <link linkend="language.variables">variable</link>. Variables always start with a dollar-sign in PHP. The variable we are interested in right now is <varname>$_SERVER['HTTP_USER_AGENT']</varname>. </para> <note> <para> <link linkend="reserved.variables.server">$_SERVER</link> is a special reserved PHP variable that contains all web server information. It is known as an autoglobal (or superglobal). See the related manual page on <link linkend="language.variables.superglobals">superglobals</link> for more information. These special variables were introduced in PHP <ulink url="&url.php.release4.1.0;">4.1.0</ulink>. Before this time, we used the older <varname>$HTTP_*_VARS</varname> arrays instead, such as <varname>$HTTP_SERVER_VARS</varname>. Although deprecated, these older variables still exist. (See also the note on <link linkend="tutorial.oldcode">old code</link>.) </para> </note> <para> To display this variable, you can simply do: </para> <para> <example> <title>Printing a variable (Array element)</title> <programlisting role="php"> <![CDATA[ <?php echo $_SERVER['HTTP_USER_AGENT']; ?> ]]> </programlisting> <para> A sample output of this script may be: </para> <screen role="html"> Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) </screen> </example> </para> <para> There are many <link linkend="language.types">types</link> of variables available in PHP. In the above example we printed an <link linkend="language.types.array">Array</link> element. Arrays can be very useful. </para> <para> <varname>$_SERVER</varname> is just one variable that PHP automatically makes available to you. A list can be seen in the <link linkend="reserved.variables">Reserved Variables</link> section of the manual or you can get a complete list of them by looking at the output of the <function>phpinfo</function> function used in the example in the previous section. </para> <para> You can put multiple PHP statements inside a PHP tag and create little blocks of code that do more than just a single echo. For example, if you want to check for Internet Explorer you can do this: </para> <para> <example> <title>Example using <link linkend="language.control-structures">control structures</link> and <link linkend="language.functions">functions</link></title> <programlisting role="php"> <![CDATA[ <?php if (strpos($_SERVER['HTTP_USER_AGENT'], 'MSIE') !== FALSE) { echo 'You are using Internet Explorer.<br />'; } ?> ]]> </programlisting> <para> A sample output of this script may be: </para> <screen role="html"> <![CDATA[ You are using Internet Explorer.<br /> ]]> </screen> </example> </para> <para> Here we introduce a couple of new concepts. We have an <link linkend="control-structures.if">if</link> statement. If you are familiar with the basic syntax used by the C language, this should look logical to you. Otherwise, you should probably pick up an introductory PHP book and read the first couple of chapters, or read the <link linkend="langref">Language Reference</link> part of the manual. You can find a list of PHP books at <ulink url="&url.php.books;">&url.php.books;</ulink>. </para> <para> The second concept we introduced was the <function>strpos</function> function call. <function>strpos</function> is a function built into PHP which searches a string for another string. In this case we are looking for <literal>'MSIE'</literal> (so-called needle) inside <varname>$_SERVER['HTTP_USER_AGENT']</varname> (so-called haystack). If the needle is found inside the haystack, the function returns the position of the needle relative to the start of the haystack. Otherwise, it returns &false;. If it does not return &false;, the <link linkend="control-structures.if">if</link> expression evaluates to &true; and the code within its {braces} is executed. Otherwise, the code is not run. Feel free to create similar examples, with <link linkend="control-structures.if">if</link>, <link linkend="control-structures.else">else</link>, and other functions such as <function>strtoupper</function> and <function>strlen</function>. Each related manual page contains examples too. If you are unsure how to use functions, you will want to read both the manual page on <link linkend="about.prototypes">how to read a function definition</link> and the section about <link linkend="language.functions">PHP functions</link>. </para> <para> We can take this a step further and show how you can jump in and out of PHP mode even in the middle of a PHP block: </para> <para> <example> <title>Mixing both HTML and PHP modes</title> <programlisting role="php"> <![CDATA[ <?php if (strpos($_SERVER['HTTP_USER_AGENT'], 'MSIE') !== FALSE) { ?> <h3>strpos() must have returned non-false</h3> <p>You are using Internet Explorer</p> <?php } else { ?> <h3>strpos() must have returned false</h3> <p>You are not using Internet Explorer</p> <?php } ?> ]]> </programlisting> <para> A sample output of this script may be: </para> <screen role="html"> <![CDATA[ <h3>strpos() must have returned non-false</h3> <p>You are using Internet Explorer</p> ]]> </screen> </example> </para> <para> Instead of using a PHP echo statement to output something, we jumped out of PHP mode and just sent straight HTML. The important and powerful point to note here is that the logical flow of the script remains intact. Only one of the HTML blocks will end up getting sent to the viewer depending on the result of <function>strpos</function>. In other words, it depends on whether the string <literal>MSIE</literal> was found or not. </para> </sect1> <sect1 id="tutorial.forms"> <title>Práce s formuláøi</title> <para> One of the most powerful features of PHP is the way it handles HTML forms. The basic concept that is important to understand is that any form element will automatically be available to your PHP scripts. Please read the manual section on <link linkend="language.variables.external">Variables from outside of PHP</link> for more information and examples on using forms with PHP. Here is an example HTML form: </para> <para> <example> <title>A simple HTML form</title> <programlisting role="html"> <![CDATA[ <form action="action.php" method="post"> <p>Your name: <input type="text" name="name" /></p> <p>Your age: <input type="text" name="age" /></p> <p><input type="submit" /></p> </form> ]]> </programlisting> </example> </para> <para> There is nothing special about this form. It is a straight HTML form with no special tags of any kind. When the user fills in this form and hits the submit button, the <filename>action.php</filename> page is called. In this file you would write something like this: </para> <para> <example> <title>Printing data from our form</title> <programlisting role="php"> <![CDATA[ Hi <?php echo $_POST['name']; ?>. You are <?php echo $_POST['age']; ?> years old. ]]> </programlisting> <para> A sample output of this script may be: </para> <screen role="html"> <![CDATA[ Hi Joe. You are 22 years old. ]]> </screen> </example> </para> <para> It should be obvious what this does. There is nothing more to it. The <varname>$_POST['name']</varname> and <varname>$_POST['age']</varname> variables are automatically set for you by PHP. Earlier we used the <varname>$_SERVER</varname> autoglobal; above we just introduced the <link linkend="reserved.variables.post">$_POST</link> autoglobal which contains all POST data. Notice how the <emphasis>method</emphasis> of our form is POST. If we used the method <emphasis>GET</emphasis> then our form information would live in the <link linkend="reserved.variables.get">$_GET</link> autoglobal instead. You may also use the <link linkend="reserved.variables.request">$_REQUEST</link> autoglobal, if you do not care about the source of your request data. It contains the merged information of GET, POST and COOKIE data. Also see the <function>import_request_variables</function> function. </para> <para> You can also deal with XForms input in PHP, although you will find yourself comfortable with the well supported HTML forms for quite some time. While working with XForms is not for beginners, you might be interested in them. We also have a <link linkend="features.xforms">short introduction to handling data received from XForms</link> in our features section. </para> </sect1> <sect1 id="tutorial.oldcode"> <title>Pou¾ití starého kódu s novými verzemi PHP</title> <para> Now that PHP has grown to be a popular scripting language, there are a lot of public repositories and libraries containing code you can reuse. The PHP developers have largely tried to preserve backwards compatibility, so a script written for an older version will run (ideally) without changes in a newer version of PHP. In practice, some changes will usually be needed. </para> <para> Two of the most important recent changes that affect old code are: <itemizedlist> <listitem> <simpara> The deprecation of the old <varname>$HTTP_*_VARS</varname> arrays (which need to be indicated as global when used inside a function or method). The following <link linkend="language.variables.superglobals">autoglobal arrays</link> were introduced in PHP <ulink url="&url.php.release4.1.0;">4.1.0</ulink>. They are: <varname>$_GET</varname>, <varname>$_POST</varname>, <varname>$_COOKIE</varname>, <varname>$_SERVER</varname>, <varname>$_FILES</varname>, <varname>$_ENV</varname>, <varname>$_REQUEST</varname>, and <varname>$_SESSION</varname>. The older <varname>$HTTP_*_VARS</varname> arrays, such as <varname>$HTTP_POST_VARS</varname>, still exist as they have since PHP 3. &avail.register-long-arrays; </simpara> </listitem> <listitem> <simpara> External variables are no longer registered in the global scope by default. In other words, as of PHP <ulink url="&url.php.release4.2.0;">4.2.0</ulink> the PHP directive <link linkend="ini.register-globals">register_globals</link> is <emphasis>off</emphasis> by default in &php.ini;. The preferred method of accessing these values is via the autoglobal arrays mentioned above. Older scripts, books, and tutorials may rely on this directive being on. If it were on, for example, one could use <varname>$id</varname> from the URL <literal>http://www.example.com/foo.php?id=42</literal>. Whether on or off, <varname>$_GET['id']</varname> is available. </simpara> </listitem> </itemizedlist> For more details on these changes, see the section on <link linkend="language.variables.predefined">predefined variables</link> and links therein. </para> </sect1> <sect1 id="tutorial.whatsnext"> <title>A co dál?</title> <para> With your new knowledge you should be able to understand most of the manual and also the various example scripts available in the example archives. You can also find other examples on the php.net websites in the links section: <ulink url="&url.php.links;">&url.php.links;</ulink>. </para> <para> To view various slide presentations that show more of what PHP can do, see the PHP Conference Material Sites: <ulink url="&url.php.conf;"> &url.php.conf;</ulink> and <ulink url="&url.php.talks;">&url.php.talks; </ulink> </para> </sect1> </chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:"../manual.ced" sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: --> http://cvs.php.net/co.php/phpdoc-cs/docweb/main.ent?r=1.1&p=1 Index: phpdoc-cs/docweb/main.ent +++ phpdoc-cs/docweb/main.ent <?xml version="1.0" encoding="iso-8859-2"?> <!-- EN-Revision: 1.17 Maintainer: luk Status: ready --> <!-- common --> <!ENTITY docweb.common.title.default 'Dokumentaèní nástroje PHP'> <!ENTITY docweb.common.all 'V¹echno'> <!ENTITY docweb.common.n-a 'N/A'> <!ENTITY docweb.common.and 'a'> <!-- common.linkname --> <!ENTITY docweb.common.linkname.subsite-homepage 'Homepage podstránek'> <!ENTITY docweb.common.linkname.request-for-comments 'Request For Comments'> <!ENTITY docweb.common.linkname.submit-rfc 'Odeslat RFC'> <!ENTITY docweb.common.linkname.rev-check 'Revision Check'> <!ENTITY docweb.common.linkname.doc-howto 'Jak na to (Documentation Howto)'> <!ENTITY docweb.common.linkname.checkent 'Kontrola URL entit'> <!ENTITY docweb.common.linkname.orphan-notes 'Orphan Notes'> <!ENTITY docweb.common.linkname.translation-info 'Informace k pøekladùm'> <!ENTITY docweb.common.linkname.entities 'Projektové entity'> <!ENTITY docweb.common.linkname.notes-stats 'Statistiky poznámek'> <!-- hyperlinks (include markup) --> <!ENTITY docweb.common.link.php-license '<a href="http://php.net/license/">Licence PHP</a>'> <!ENTITY docweb.common.link.doc-license ' <a href="mailto:doc-license@lists.php.net">doc-license@lists.php.net</a>'> <!-- common.projects --> <!ENTITY docweb.common.project.php 'PHP'> <!ENTITY docweb.common.project.pear 'PEAR'> <!ENTITY docweb.common.project.pecl 'PECL'> <!ENTITY docweb.common.project.php-gtk 'PHP-<span class="logo-g">G</span><span class="logo-t">T</span><span class="logo-k">K</span>'> <!ENTITY docweb.common.project.smarty 'Smarty'> <!ENTITY docweb.common.project.livedocs 'Livedocs'> <!-- common.header --> <!ENTITY docweb.common.header.welcome 'Vítejte!'> <!ENTITY docweb.common.header.contact 'Kontakt'> <!ENTITY docweb.common.header.checkent 'Kontrola URL entit'> <!ENTITY docweb.common.header.revcheck 'Revcheck'> <!ENTITY docweb.common.header.orphan-notes 'Orphan Notes'> <!ENTITY docweb.common.header.currently-focused 'Aktuálnì zamìøeno na'> <!ENTITY docweb.common.header.insite-context-nav 'Vnitroserverová kontextová navigace'> <!ENTITY docweb.common.header.offsite-context-nav 'Mimoserverová kontextová navigace'> <!ENTITY docweb.common.header.credits 'Website Credits'> <!ENTITY docweb.common.header.copyright 'Copyright'> <!ENTITY docweb.common.header.error 'Chyba'> <!ENTITY docweb.common.header.project-doc-bugs 'Chyby v projektu (dokumentaci)'> <!ENTITY docweb.common.header.open-bugs 'otevøené chyby'> <!ENTITY docweb.common.header.entities 'Projektové entity'> <!ENTITY docweb.common.header.login 'Pøihlá¹ení'> <!-- common.footer --> <!ENTITY docweb.common.footer.copyright 'Copyright'> <!ENTITY docweb.common.footer.copyright-text 'Dokumentaèní týmy PHP - v¹echna práva vyhrazena'> <!ENTITY docweb.common.footer.credits 'Credits'> <!ENTITY docweb.common.footer.contact 'Kontakt'> <!-- home --> <!ENTITY docweb.home.header.what-is 'K èemu je tato stránka?'> <!ENTITY docweb.home.text.what-is "Existují rùzné dokumentaèní týmy, které ponìkud oddìlenì pracují na svých podprojektech z PHP.net. Jen nìkolik lidí je zapojeno souèasnì ve více ne¾ jednom dokumentaèním projektu, a to omezuje sdílení know-how, které by jinak bylo mo¾né a ¾ádoucí. V¹echny dokumentaèní týmy pou¾ívají èasnou vìtev pùvodního systému pro sestavování PHP manuálu. Tyto systémy se vyvíjely nezávisle a pøíle¾itostnì pøebíraly nìkterá zlep¹ení (dokumentaèní tým PEAR napøíklad pou¾ívá variantu revchecku vyvíjenou pro phpdoc). Tyto stránky mají za cíl uèinit dokumentaèní úsilí soustøedìnìj¹í a poskytnout více nástrojù a informací pro autory a pøekladatele manuálù."> <!ENTITY docweb.home.header.join-us 'Pøipojte se k nám!'> <!ENTITY docweb.home.text.join-us "Vývojáøi roz¹íøení PHP mají v¹ichni pøístup do dokumentaèních modulù, pøesto¾e rùzné projekty mají rùznou politiku pøijímání pøíspìvkù. Jste vítáni k pøipojení se k na¹emu úsilí! Psaní dokumentace k roz¹íøením je druhou nejlep¹í vìcí po samotné implementaci roz¹íøení, zajímáte-li se o schopnosti, mo¾nosti a vyu¾ití i v extrémních podmínkách. Máme také pøelo¾ené verze rùzných manuálù, a vìt¹ina pøekladatelských týmù v¾dy potøebuje více pomocných rukou. Máte-li zájem, mìli byste kontaktovat pøíslu¹né fórum. Projekty a pøeklady mají samostatná fóra."> <!-- contact --> <!ENTITY docweb.contact.license.header 'Otázky k licencování?'> <!ENTITY docweb.contact.license.text 'Máte-li otázky týkající se licencování, kontaktuje prosím veøejnì archivované fórum <a href="mailto:doc-license@lists.php.net">doc-license@lists.php.net</a>. Jiné otázky ke stránkám dokumentaèních nástrojù PHP pi¹te prosím na na¹e vlastní veøejnì archivované fórum (<a href="mailto:doc-web@lists.php.net">doc-web@lists.php.net</a>). Jiné dokumentaèní týmy mají svá vlastní e-mailová fóra..'> <!-- credits --> <!ENTITY docweb.credits.subhead 'Následující lidé pomohli ke vzniku tìchto stránek. Jsme jim za to velice vdìèni.'> <!ENTITY docweb.credits.section.admin 'Správa serveru'> <!ENTITY docweb.credits.section.devs 'Vývoj stránek'> <!ENTITY docweb.credits.section.php-services 'Slu¾by PHP.net (CVS, e-mailová fóra apod.)'> <!ENTITY docweb.credits.section.icons 'Pou¾íváme také pìkné ikony, jejich¾ autorem je'> <!ENTITY docweb.credits.php-systems 'Systémový administraèní tým PHP.net'> <!-- copyright --> <!ENTITY docweb.copyright.section.source 'Source Code Copyright (práva je zdrojovému jódu)'> <!ENTITY docweb.copyright.section.doc 'Documentation Copyright (práva k dokumentaci)'> <!ENTITY docweb.copyright.source 'Zdrojový kód stránek dokumentaèních nástrojù PHP je k dispozici pod &docweb.common.link.php-license;. Pro více informací a seznam sutorù viz poznámky ve zdrojovém kódu.'> <!ENTITY docweb.copyright.doc 'Dokumentace k rùzným projektùm, které udr¾ujeme pohromadì, jsou pod rùznými licencemi, tak¾e pro více informací se musíte podívat na copyrightové poznámky v pøíslu¹ných manuálech. Máte-li otázky, které nejsou v licencích zodpovìzeny, ptejte se prosím na &docweb.common.link.doc-license;.'> <!-- login page --> <!ENTITY docweb.login.subhead 'Pøihlá¹ení na stránky dokumentaèního týmu PHP.'> <!ENTITY docweb.login.text '<strong>Poznámka:</strong> Pokud chcete pouze prohlí¾et tyto stránky, nemusíte se pøihla¹ovat. Pro v¹echny operace vy¾adující autentizaci budete automaticky pøesmìrováni na tento formuláø.'> <!-- error codes --> <!ENTITY docweb.error.404 'Soubor nenalezen'> <!ENTITY docweb.error.nomesg 'Není k dispozici ¾ádná zpráva.'> <!-- url entities --> <!ENTITY docweb.checkent.result.success 'ÚSPÌCH'> <!ENTITY docweb.checkent.result.unknown-host 'Neznámý hostitel'> <!ENTITY docweb.checkent.result.ftp-connect 'Pøipojení selhalo (FTP)'> <!ENTITY docweb.checkent.result.ftp-login 'Pøihlá¹ení selhalo (FTP)'> <!ENTITY docweb.checkent.result.ftp-no-file 'Soubor nenalezen (FTP)'> <!ENTITY docweb.checkent.result.http-connect 'Pøipojení selhalo (HTTP)'> <!ENTITY docweb.checkent.result.http-moved 'Prostøedek pøemístìn (HTTP)'> <!ENTITY docweb.checkent.result.http-wrong-header 'Chybná hlavièka (HTTP)'> <!ENTITY docweb.checkent.result.http-internal-error 'Vnitøní chyba (HTTP)'> <!ENTITY docweb.checkent.result.http-not-found 'Prostøedek nenalezen (HTTP)'>
« previous php.doc.cs (#146) next »